search for: dc197e236d50

...from the "father" of > Slackware himself that I should be able to upgrade this package w/o too much > difficulty. > > --Mark > If I find the GUID for a DC, then use it in searches, I get results like these: adminuser at rpidc1:~ $ host -t CNAME fb453823-737c-4a8b-93e1-dc197e236d50 fb453823-737c-4a8b-93e1-dc197e236d50 has no CNAME record Doing an 'A' record search using the GUIDs FQDN, gets me this: adminuser at rpidc1:~ $ host -t A fb453823-737c-4a8b-93e1-dc197e236d50._msdcs.samdom.example.com. fb453823-737c-4a8b-93e1-dc197e236d50._msdcs.samdom.example.com is an...

...are himself that I should be able to upgrade this package w/o too much > > difficulty. > > > > --Mark > > > > If I find the GUID for a DC, then use it in searches, I get results like > these: > > adminuser at rpidc1:~ $ host -t CNAME fb453823-737c-4a8b-93e1-dc197e236d50 > fb453823-737c-4a8b-93e1-dc197e236d50 has no CNAME record > > Doing an 'A' record search using the GUIDs FQDN, gets me this: > > adminuser at rpidc1:~ $ host -t A > fb453823-737c-4a8b-93e1-dc197e236d50._msdcs.samdom.example.com. > fb453823-737c-4a8b-93e1-dc197e236d50....

...l > > > host: idnkit idn_encodename to idn failed: prohibited character found > > > > That is strange, if I obtain the GUID's on my DCs and run a similar > > command, I get this: > > > > adminuser at rpidc1:~ $ host -t A > > fb453823-737c-4a8b-93e1-dc197e236d50._msdcs.samdom.example.com > > fb453823-737c-4a8b-93e1-dc197e236d50._msdcs.samdom.example.com is an > > alias for rpidc1.samdom.example.com. > > rpidc1.samdom.example.com has address 192.168.1.2 > > > > Rowland > > It could be a difference in host command version...