Displaying 7 results from an estimated 7 matches for "zatprdc001".
2018 Oct 31
2
Internal DNS migrate to Bind9_DLZ
Hello Rowland,
I have already checked and the DN's are in AD, see attached.
SOA:
<domain>.corp. 3600 IN SOA psad102zadprh.<domain>.corp. . 9766
3600 600 86400 3600
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...
2018 Oct 31
0
Internal DNS migrate to Bind9_DLZ
...ctor at gmail.com> wrote:
> Hello Rowland,
>
> I have already checked and the DN's are in AD, see attached.
>
> SOA:
> <domain>.corp. 3600 IN SOA psad102zadprh.<domain>.corp. .
> 9766 3600 600 86400 3600
>
> 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.<do...
2018 Oct 31
3
Internal DNS migrate to Bind9_DLZ
...llo Rowland,
> >
> > I have already checked and the DN's are in AD, see attached.
> >
> > SOA:
> > <domain>.corp. 3600 IN SOA psad102zadprh.<domain>.corp. .
> > 9766 3600 600 86400 3600
> >
> > 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 N...
2018 Nov 01
0
Internal DNS migrate to Bind9_DLZ
...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
> demoted DC, old hostname, cannot be found in AD
> <domain>.corp. 3600 IN NS prdc002zacprh.<domain>.corp. ->
> New rebuild, new hostname, RHEL6 to RHEL7 upgrade
> <domain>.corp. 3600 IN NS psad102zadprh.<dom...
2018 Nov 01
2
Internal DNS migrate to Bind9_DLZ
....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
demoted DC, old hostname, cannot be found in AD
<domain>.corp. 3600 IN NS prdc002zacprh.<domain>.corp. -> New
rebuild, new hostname, RHEL6 to RHEL7 upgrade
<domain>.corp. 3600 IN NS psad102zadprh.<domain>.corp. ->...
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
...srh.<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
> > demoted DC, old hostname, cannot be found in AD
> > <domain>.corp. 3600 IN NS prdc002zacprh.<domain>.corp. ->
> > New rebuild, new hostname, RHEL6 to RHEL7 upgrade
> > <domain>.corp. 3600 IN NS p...