Displaying 7 results from an estimated 7 matches for "prdc001zafsrh".
Did you mean:
prdc001zacprh
2018 Oct 31
2
Internal DNS migrate to Bind9_DLZ
...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 prdc003zacprh.<domain>.corp.
<domain>.corp. 3600 IN NS...
2018 Oct 31
3
Internal DNS migrate to Bind9_DLZ
...in>.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 prdc003zacprh.<domain>.corp.
> > &...
2018 Oct 31
0
Internal DNS migrate to Bind9_DLZ
...:
> <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 prdc003zacprh.<domain>.corp.
> <domain>.corp....
2018 Nov 01
0
Internal DNS migrate to Bind9_DLZ
...experts :)
>
> I have rejoined all my DC's with new names, see below.
> ;; ANSWER SECTION:
> <domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. ->
> New rebuild, new hostname, RHEL6 to RHEL7 upgrade
> <domain>.corp. 3600 IN NS prdc001zafsrh.<domain>.corp. ->
> New rebuild, new hostname, RHEL6 to RHEL7 upgrade
> <domain>.corp. 3600 IN NS prdc003zacprh.<domain>.corp. ->
> New rebuild, new hostname, RHEL6 to RHEL7 upgrade
> <domain>.corp. 3600 IN NS zatprdc001.<domain&g...
2018 Nov 01
2
Internal DNS migrate to Bind9_DLZ
...etime now, hence I came to
the experts :)
I have rejoined all my DC's with new names, see below.
;; ANSWER SECTION:
<domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. -> New
rebuild, new hostname, RHEL6 to RHEL7 upgrade
<domain>.corp. 3600 IN NS prdc001zafsrh.<domain>.corp. -> New
rebuild, new hostname, RHEL6 to RHEL7 upgrade
<domain>.corp. 3600 IN NS prdc003zacprh.<domain>.corp. -> New
rebuild, new hostname, RHEL6 to RHEL7 upgrade
<domain>.corp. 3600 IN NS zatprdc001.<domain>.corp. -> Old
d...
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. ;-)
2018 Nov 01
1
Internal DNS migrate to Bind9_DLZ
...t; I have rejoined all my DC's with new names, see below.
> > ;; ANSWER SECTION:
> > <domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. ->
> > New rebuild, new hostname, RHEL6 to RHEL7 upgrade
> > <domain>.corp. 3600 IN NS prdc001zafsrh.<domain>.corp. ->
> > New rebuild, new hostname, RHEL6 to RHEL7 upgrade
> > <domain>.corp. 3600 IN NS prdc003zacprh.<domain>.corp. ->
> > New rebuild, new hostname, RHEL6 to RHEL7 upgrade
> > <domain>.corp. 3600 IN NS zat...