search for: prdc001zacprh

Displaying 7 results from an estimated 7 matches for "prdc001zacprh".

Internal DNS migrate to Bind9_DLZ
2018 Oct 31
2
Internal DNS migrate to Bind9_DLZ
...600 See below NS, but the 1st NS (zatprdc001) doesn't exsit, and I cannot find it anywhere. NS: <domain>.corp. 3600 IN NS zatprdc001.<domain>.corp. <domain>.corp. 3600 IN NS psad102zadprh.<domain>.corp. <domain>.corp. 3600 IN NS prdc001zacprh.<domain>.corp. <domain>.corp. 3600 IN NS prdc001zafsrh.<domain>.corp. <domain>.corp. 3600 IN NS prdc001zatcrh.<domain>.corp. <domain>.corp. 3600 IN NS prdc002zacprh.<domain>.corp. <domain>.corp. 3600 IN NS...
Internal DNS migrate to Bind9_DLZ
2018 Oct 31
3
Internal DNS migrate to Bind9_DLZ
...sn't exsit, and I cannot > > find it anywhere. > > NS: > > <domain>.corp. 3600 IN NS zatprdc001.<domain>.corp. > > <domain>.corp. 3600 IN NS psad102zadprh.<domain>.corp. > > <domain>.corp. 3600 IN NS prdc001zacprh.<domain>.corp. > > <domain>.corp. 3600 IN NS prdc001zafsrh.<domain>.corp. > > <domain>.corp. 3600 IN NS prdc001zatcrh.<domain>.corp. > > <domain>.corp. 3600 IN NS prdc002zacprh.<domain>.corp. > > &...
Internal DNS migrate to Bind9_DLZ
2018 Oct 31
0
Internal DNS migrate to Bind9_DLZ
...e 1st NS (zatprdc001) doesn't exsit, and I cannot > find it anywhere. > NS: > <domain>.corp. 3600 IN NS zatprdc001.<domain>.corp. > <domain>.corp. 3600 IN NS psad102zadprh.<domain>.corp. > <domain>.corp. 3600 IN NS prdc001zacprh.<domain>.corp. > <domain>.corp. 3600 IN NS prdc001zafsrh.<domain>.corp. > <domain>.corp. 3600 IN NS prdc001zatcrh.<domain>.corp. > <domain>.corp. 3600 IN NS prdc002zacprh.<domain>.corp. > <domain>.corp....
Internal DNS migrate to Bind9_DLZ
2018 Nov 01
0
Internal DNS migrate to Bind9_DLZ
...NS psad102zadprh.<domain>.corp. -> > New rebuild, new hostname, RHEL6 to RHEL7 upgrade > <domain>.corp. 3600 IN NS prdc001zatcrh.<domain>.corp. -> > New rebuild, new hostname, RHEL6 to RHEL7 upgrade > <domain>.corp. 3600 IN NS prdc001zacprh.<domain>.corp. -> > New rebuild, new hostname, RHEL6 to RHEL7 upgrade > Just a thought ;-) > Here is the "/etc/resolv.conf" > I have tried different changes in the /etc/resolv.conf as well > $ cat /etc/resolv.conf > # Generated by NetworkManager > search &...
Internal DNS migrate to Bind9_DLZ
2018 Nov 01
2
Internal DNS migrate to Bind9_DLZ
....corp. 3600 IN NS psad102zadprh.<domain>.corp. -> New rebuild, new hostname, RHEL6 to RHEL7 upgrade <domain>.corp. 3600 IN NS prdc001zatcrh.<domain>.corp. -> New rebuild, new hostname, RHEL6 to RHEL7 upgrade <domain>.corp. 3600 IN NS prdc001zacprh.<domain>.corp. -> New rebuild, new hostname, RHEL6 to RHEL7 upgrade Here is the "/etc/resolv.conf" I have tried different changes in the /etc/resolv.conf as well $ cat /etc/resolv.conf # Generated by NetworkManager search <domain>.corp <domain2>.corp <domain3>....
Internal DNS migrate to Bind9_DLZ
2018 Nov 01
1
Internal DNS migrate to Bind9_DLZ
...prh.<domain>.corp. -> > > New rebuild, new hostname, RHEL6 to RHEL7 upgrade > > <domain>.corp. 3600 IN NS prdc001zatcrh.<domain>.corp. -> > > New rebuild, new hostname, RHEL6 to RHEL7 upgrade > > <domain>.corp. 3600 IN NS prdc001zacprh.<domain>.corp. -> > > New rebuild, new hostname, RHEL6 to RHEL7 upgrade > > > > Just a thought ;-) > > > Here is the "/etc/resolv.conf" > > I have tried different changes in the /etc/resolv.conf as well > > $ cat /etc/resolv.conf > > #...
FW: Internal DNS migrate to Bind9_DLZ
2018 Oct 31
3
FW: Internal DNS migrate to Bind9_DLZ
Hai,   I've checked out the log you send and i re-read the complete thread.   Based on thats done and what i did see in you logs now, looks like a  * (wildcard)  entry is giving the problem. But i am not sure of that, the wildcard bugs should be fixed, when i look in bugzilla.  (#10435 #12952 )   I've forwarded the mail to Rowland also before we go throw things at you again. ;-)