RE: DNS Reverse lookup question

2008-10-23 Thread RichardMcClary 
OK, my bad...  they had about 250 nodes at that location.  They had 3 
locations in NYC w/about 500 total.  Still, they had "10.1.1.x" before we 
did.
--
Richard McClary, Systems Administrator
ASPCA Knowledge Management
1717 S Philo Rd, Ste 36, Urbana, IL  61802
217-337-9761
http://www.aspca.org


"Steven M. Caesare" <[EMAIL PROTECTED]> wrote on 10/22/2008 11:23:57 
AM:

> You had a /24 with 500 nodes?
> 
> -sc
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, October 22, 2008 10:02 AM
> > To: NT System Admin Issues
> > Subject: RE: DNS Reverse lookup question
> > 
> > We had something like this pop up a couple of years ago, although DNS
> > was
> > not yet involved.  We were simply making a VPN connection.  Our
> > 10.1.1.x
> > network had only about 130 nodes; the other 10.1.1.x had about 500
> > nodes.
> > Guess who the poor #@&% was who had to come in at 11 PM and spend 10
> > hours
> > changing one network to a 10.1.2.x network...
> > --
> > Richard McClary, Systems Administrator
> > ASPCA Knowledge Management
> > 1717 S Philo Rd, Ste 36, Urbana, IL  61802
> > 217-337-9761
> > http://www.aspca.org
> > 
> > 
> > "Michael B. Smith" <[EMAIL PROTECTED]> wrote on
> > 10/21/2008
> > 04:56:19 PM:
> > 
> > > Either take the pain now, or take it later…
> > >
> > > Regards,
> > >
> > > Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
> > > My blog: http://TheEssentialExchange.com/blogs/michael
> > > Link with me at: http://www.linkedin.com/in/theessentialexchange
> > >
> > > From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, October 21, 2008 1:31 PM
> > > To: NT System Admin Issues
> > > Subject: RE: DNS Reverse lookup question
> > >
> > > The problem is the subnet already exists in both domains...
> > >
> > > -Brian
> > >
> > >
> > >
> > > From: Michael B. Smith [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, October 21, 2008 11:49 AM
> > > To: NT System Admin Issues
> > > Subject: RE: DNS Reverse lookup question
> > > You can use a stub domain or a forwarding domain.
> > >
> > > Regards,
> > >
> > > Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
> > > My blog: http://TheEssentialExchange.com/blogs/michael
> > > Link with me at: http://www.linkedin.com/in/theessentialexchange
> > >
> > > From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, October 21, 2008 12:47 PM
> > > To: NT System Admin Issues
> > > Subject: DNS Reverse lookup question
> > >
> > > Here is the situation:
> > > 1 IP range has servers from 2 different domains
> > >
> > > DNS servers (AD integrated) for each domain have entries for the
> > > servers in that domain
> > >
> > > If I do a reverse lookup from a machine that is pointed to the
> > > "right" DNS server it works, otherwise I get a non-existent domain.
> > > Hw do you solve this?  Do you manually put in PTR records for all
> > > the servers in the opposite domain?
> > >
> > > Example:
> > > Server1.corp.local is at 10.1.1.10
> > >
> > > Server2.division.local is at 10.1.1.20
> > >
> > > Client1.corp.local is at 10.100.100.100 with DNS server pointed to
> > > DNSserver.corp.local
> > > Client2.division.local is at 10.200.200.200 with DNS server pointed
> > > to DNSserver.division.local
> > >
> > > nslookup from client1 for 10.1.1.10 returns Server1
> > > nslookup from client1 for 10.1.1.20 returns non-existent domain
> > >
> > > nslookup from Client2 for 10.1.1.10 returns non-existent domain
> > > nslookup from Client2 for 10.1.1.20 returns Server2
> > >
> > > nslookup by name (forward lookup) works everywhere.
> > >
> > > Brian Webb - MCSE
> > > TDS Corporate IS, Windows Server Platform Team
> > > Senior Systems Administrator
> > >
> > > "When stuck on a problem as often can be, try to remember G.B.T.T.D.
> > > (Go Back To The Definition)". - Dave Seybold
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > 
> > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
> 
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

RE: DNS Reverse lookup question

2008-10-22 Thread Steven M. Caesare 
You had a /24 with 500 nodes?

-sc

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 22, 2008 10:02 AM
> To: NT System Admin Issues
> Subject: RE: DNS Reverse lookup question
> 
> We had something like this pop up a couple of years ago, although DNS
> was
> not yet involved.  We were simply making a VPN connection.  Our
> 10.1.1.x
> network had only about 130 nodes; the other 10.1.1.x had about 500
> nodes.
> Guess who the poor #@&% was who had to come in at 11 PM and spend 10
> hours
> changing one network to a 10.1.2.x network...
> --
> Richard McClary, Systems Administrator
> ASPCA Knowledge Management
> 1717 S Philo Rd, Ste 36, Urbana, IL  61802
> 217-337-9761
> http://www.aspca.org
> 
> 
> "Michael B. Smith" <[EMAIL PROTECTED]> wrote on
> 10/21/2008
> 04:56:19 PM:
> 
> > Either take the pain now, or take it later…
> >
> > Regards,
> >
> > Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
> > My blog: http://TheEssentialExchange.com/blogs/michael
> > Link with me at: http://www.linkedin.com/in/theessentialexchange
> >
> > From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 21, 2008 1:31 PM
> > To: NT System Admin Issues
> > Subject: RE: DNS Reverse lookup question
> >
> > The problem is the subnet already exists in both domains...
> >
> > -Brian
> >
> >
> >
> > From: Michael B. Smith [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 21, 2008 11:49 AM
> > To: NT System Admin Issues
> > Subject: RE: DNS Reverse lookup question
> > You can use a stub domain or a forwarding domain.
> >
> > Regards,
> >
> > Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
> > My blog: http://TheEssentialExchange.com/blogs/michael
> > Link with me at: http://www.linkedin.com/in/theessentialexchange
> >
> > From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 21, 2008 12:47 PM
> > To: NT System Admin Issues
> > Subject: DNS Reverse lookup question
> >
> > Here is the situation:
> > 1 IP range has servers from 2 different domains
> >
> > DNS servers (AD integrated) for each domain have entries for the
> > servers in that domain
> >
> > If I do a reverse lookup from a machine that is pointed to the
> > "right" DNS server it works, otherwise I get a non-existent domain.
> > Hw do you solve this?  Do you manually put in PTR records for all
> > the servers in the opposite domain?
> >
> > Example:
> > Server1.corp.local is at 10.1.1.10
> >
> > Server2.division.local is at 10.1.1.20
> >
> > Client1.corp.local is at 10.100.100.100 with DNS server pointed to
> > DNSserver.corp.local
> > Client2.division.local is at 10.200.200.200 with DNS server pointed
> > to DNSserver.division.local
> >
> > nslookup from client1 for 10.1.1.10 returns Server1
> > nslookup from client1 for 10.1.1.20 returns non-existent domain
> >
> > nslookup from Client2 for 10.1.1.10 returns non-existent domain
> > nslookup from Client2 for 10.1.1.20 returns Server2
> >
> > nslookup by name (forward lookup) works everywhere.
> >
> > Brian Webb - MCSE
> > TDS Corporate IS, Windows Server Platform Team
> > Senior Systems Administrator
> >
> > "When stuck on a problem as often can be, try to remember G.B.T.T.D.
> > (Go Back To The Definition)". - Dave Seybold
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> 
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

RE: DNS Reverse lookup question

2008-10-22 Thread RichardMcClary 
We had something like this pop up a couple of years ago, although DNS was 
not yet involved.  We were simply making a VPN connection.  Our 10.1.1.x 
network had only about 130 nodes; the other 10.1.1.x had about 500 nodes. 
Guess who the poor #@&% was who had to come in at 11 PM and spend 10 hours 
changing one network to a 10.1.2.x network...
--
Richard McClary, Systems Administrator
ASPCA Knowledge Management
1717 S Philo Rd, Ste 36, Urbana, IL  61802
217-337-9761
http://www.aspca.org


"Michael B. Smith" <[EMAIL PROTECTED]> wrote on 10/21/2008 
04:56:19 PM:

> Either take the pain now, or take it later…
> 
> Regards,
> 
> Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
> My blog: http://TheEssentialExchange.com/blogs/michael
> Link with me at: http://www.linkedin.com/in/theessentialexchange
> 
> From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 21, 2008 1:31 PM
> To: NT System Admin Issues
> Subject: RE: DNS Reverse lookup question
> 
> The problem is the subnet already exists in both domains...
> 
> -Brian
> 
> 
> 
> From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 21, 2008 11:49 AM
> To: NT System Admin Issues
> Subject: RE: DNS Reverse lookup question
> You can use a stub domain or a forwarding domain.
> 
> Regards,
> 
> Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
> My blog: http://TheEssentialExchange.com/blogs/michael
> Link with me at: http://www.linkedin.com/in/theessentialexchange
> 
> From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 21, 2008 12:47 PM
> To: NT System Admin Issues
> Subject: DNS Reverse lookup question
> 
> Here is the situation:
> 1 IP range has servers from 2 different domains 
> 
> DNS servers (AD integrated) for each domain have entries for the 
> servers in that domain
> 
> If I do a reverse lookup from a machine that is pointed to the 
> "right" DNS server it works, otherwise I get a non-existent domain. 
> Hw do you solve this?  Do you manually put in PTR records for all 
> the servers in the opposite domain?
> 
> Example:
> Server1.corp.local is at 10.1.1.10
> 
> Server2.division.local is at 10.1.1.20
> 
> Client1.corp.local is at 10.100.100.100 with DNS server pointed to 
> DNSserver.corp.local
> Client2.division.local is at 10.200.200.200 with DNS server pointed 
> to DNSserver.division.local
> 
> nslookup from client1 for 10.1.1.10 returns Server1
> nslookup from client1 for 10.1.1.20 returns non-existent domain
> 
> nslookup from Client2 for 10.1.1.10 returns non-existent domain
> nslookup from Client2 for 10.1.1.20 returns Server2
> 
> nslookup by name (forward lookup) works everywhere.
> 
> Brian Webb - MCSE
> TDS Corporate IS, Windows Server Platform Team
> Senior Systems Administrator
> 
> "When stuck on a problem as often can be, try to remember G.B.T.T.D.
> (Go Back To The Definition)". - Dave Seybold
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

RE: DNS Reverse lookup question

2008-10-21 Thread Troy Meyer 
Wouldn't a secondary zone on each DNS server for the opposing domain make this 
work?

You may need to specify the IP of each destination DNS server on each host DNS 
server (see zone transfers), but you should be golden with that.


-troy


-Original Message-
From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 9:47 AM
To: NT System Admin Issues
Subject: DNS Reverse lookup question

Here is the situation:
1 IP range has servers from 2 different domains

DNS servers (AD integrated) for each domain have entries for the servers in 
that domain

If I do a reverse lookup from a machine that is pointed to the "right" DNS 
server it works, otherwise I get a non-existent domain.  Hw do you solve this?  
Do you manually put in PTR records for all the servers in the opposite domain?

Example:
Server1.corp.local is at 10.1.1.10

Server2.division.local is at 10.1.1.20

Client1.corp.local is at 10.100.100.100 with DNS server pointed to 
DNSserver.corp.local
Client2.division.local is at 10.200.200.200 with DNS server pointed to 
DNSserver.division.local

nslookup from client1 for 10.1.1.10 returns Server1
nslookup from client1 for 10.1.1.20 returns non-existent domain

nslookup from Client2 for 10.1.1.10 returns non-existent domain
nslookup from Client2 for 10.1.1.20 returns Server2

nslookup by name (forward lookup) works everywhere.

Brian Webb - MCSE
TDS Corporate IS, Windows Server Platform Team
Senior Systems Administrator

"When stuck on a problem as often can be, try to remember G.B.T.T.D. (Go Back 
To The Definition)". - Dave Seybold









~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

Re: DNS Reverse lookup question

2008-10-21 Thread wjh 
Do you mean that the two domains share a network, or that the two 
networks use the same IP addressing?


Webb, Brian (Corp) wrote:
@font-face { font-family: Cambria Math; } @font-face { font-family: 
Calibri; } @font-face { font-family: Tahoma; } @font-face { 
font-family: Consolas; } @font-face { font-family: Kristen ITC; } 
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; } 
P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: 
"Times New Roman","serif" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 
0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } DIV.MsoNormal { 
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New 
Roman","serif" } A:link { COLOR: blue; TEXT-DECORATION: underline; 
mso-style-priority: 99 } SPAN.MsoHyperlink { COLOR: blue; 
TEXT-DECORATION: underline; mso-style-priority: 99 } A:visited { 
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } 
SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline; 
mso-style-priority: 99 } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; 
MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; 
mso-style-priority: 99; mso-margin-top-alt: auto; 
mso-margin-bottom-alt: auto } PRE { FONT-SIZE: 10pt; MARGIN: 0in 0in 
0pt; FONT-FAMILY: "Courier New"; mso-style-priority: 99; 
mso-style-link: "HTML Preformatted Char" } SPAN.HTMLPreformattedChar { 
FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "HTML 
Preformatted"; mso-style-name: "HTML Preformatted Char" } 
SPAN.EmailStyle20 { COLOR: #1f497d; FONT-FAMILY: 
"Calibri","sans-serif"; mso-style-type: personal-reply } 
.MsoChpDefault { FONT-SIZE: 10pt; mso-style-type: export-only } 
DIV.Section1 { page: Section1 }

The problem is the subnet already exists in both domains...
-Brian

--------
*From:* Michael B. Smith [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, October 21, 2008 11:49 AM
*To:* NT System Admin Issues
*Subject:* RE: DNS Reverse lookup question

You can use a stub domain or a forwarding domain.

Regards,

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

*From:* Webb, Brian (Corp) [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, October 21, 2008 12:47 PM
*To:* NT System Admin Issues
*Subject:* DNS Reverse lookup question

Here is the situation:

1 IP range has servers from 2 different domains

DNS servers (AD integrated) for each domain have entries for the 
servers in that domain


If I do a reverse lookup from a machine that is pointed to the "right" 
DNS server it works, otherwise I get a non-existent domain.  Hw do you 
solve this?  Do you manually put in PTR records for all the servers in 
the opposite domain?


Example:

Server1.corp.local is at 10.1.1.10

Server2.division.local is at 10.1.1.20

Client1.corp.local is at 10.100.100.100 with DNS server pointed to 
DNSserver.corp.local


Client2.division.local is at 10.200.200.200 with DNS server pointed to 
DNSserver.division.local


nslookup from client1 for 10.1.1.10 returns Server1

nslookup from client1 for 10.1.1.20 returns non-existent domain

nslookup from Client2 for 10.1.1.10 returns non-existent domain

nslookup from Client2 for 10.1.1.20 returns Server2

nslookup by name (forward lookup) works everywhere.

Brian Webb - MCSE
TDS Corporate IS, Windows Server Platform Team
Senior Systems Administrator

"When stuck on a problem as often can be, try to remember G.B.T.T.D. 
(Go Back To The Definition)". - Dave Seybold


 

 

 



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

RE: DNS Reverse lookup question

2008-10-21 Thread Michael B. Smith 
Either take the pain now, or take it later.

 

Regards,

 

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

 

From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 1:31 PM
To: NT System Admin Issues
Subject: RE: DNS Reverse lookup question

 

The problem is the subnet already exists in both domains...

 

-Brian

 

 

  _  

From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 11:49 AM
To: NT System Admin Issues
Subject: RE: DNS Reverse lookup question

You can use a stub domain or a forwarding domain.

 

Regards,

 

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

 

From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 12:47 PM
To: NT System Admin Issues
Subject: DNS Reverse lookup question

 

Here is the situation:

1 IP range has servers from 2 different domains 

 

DNS servers (AD integrated) for each domain have entries for the servers in
that domain

 

If I do a reverse lookup from a machine that is pointed to the "right" DNS
server it works, otherwise I get a non-existent domain.  Hw do you solve
this?  Do you manually put in PTR records for all the servers in the
opposite domain?

 

Example:

Server1.corp.local is at 10.1.1.10

 

Server2.division.local is at 10.1.1.20

 

Client1.corp.local is at 10.100.100.100 with DNS server pointed to
DNSserver.corp.local

Client2.division.local is at 10.200.200.200 with DNS server pointed to
DNSserver.division.local

 

nslookup from client1 for 10.1.1.10 returns Server1

nslookup from client1 for 10.1.1.20 returns non-existent domain

 

nslookup from Client2 for 10.1.1.10 returns non-existent domain

nslookup from Client2 for 10.1.1.20 returns Server2

 

nslookup by name (forward lookup) works everywhere.

 

Brian Webb - MCSE
TDS Corporate IS, Windows Server Platform Team
Senior Systems Administrator

"When stuck on a problem as often can be, try to remember G.B.T.T.D. (Go
Back To The Definition)". - Dave Seybold

 

 

 

 

 

 

 

 

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

RE: DNS Reverse lookup question

2008-10-21 Thread Webb, Brian (Corp) 
The problem is the subnet already exists in both domains...
 
-Brian

 



From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 11:49 AM
To: NT System Admin Issues
Subject: RE: DNS Reverse lookup question



You can use a stub domain or a forwarding domain.

 

Regards,

 

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

 

From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 12:47 PM
To: NT System Admin Issues
Subject: DNS Reverse lookup question

 

Here is the situation:

1 IP range has servers from 2 different domains 

 

DNS servers (AD integrated) for each domain have entries for the servers
in that domain

 

If I do a reverse lookup from a machine that is pointed to the "right"
DNS server it works, otherwise I get a non-existent domain.  Hw do you
solve this?  Do you manually put in PTR records for all the servers in
the opposite domain?

 

Example:

Server1.corp.local is at 10.1.1.10

 

Server2.division.local is at 10.1.1.20

 

Client1.corp.local is at 10.100.100.100 with DNS server pointed to
DNSserver.corp.local

Client2.division.local is at 10.200.200.200 with DNS server pointed to
DNSserver.division.local

 

nslookup from client1 for 10.1.1.10 returns Server1

nslookup from client1 for 10.1.1.20 returns non-existent domain

 

nslookup from Client2 for 10.1.1.10 returns non-existent domain

nslookup from Client2 for 10.1.1.20 returns Server2

 

nslookup by name (forward lookup) works everywhere.

 

Brian Webb - MCSE
TDS Corporate IS, Windows Server Platform Team
Senior Systems Administrator

"When stuck on a problem as often can be, try to remember G.B.T.T.D. (Go
Back To The Definition)". - Dave Seybold

 

 

 

 


 

 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

RE: DNS Reverse lookup question

2008-10-21 Thread Michael B. Smith 
You can use a stub domain or a forwarding domain.

 

Regards,

 

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP

My blog: http://TheEssentialExchange.com/blogs/michael

Link with me at: http://www.linkedin.com/in/theessentialexchange

 

From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, October 21, 2008 12:47 PM
To: NT System Admin Issues
Subject: DNS Reverse lookup question

 

Here is the situation:

1 IP range has servers from 2 different domains 

 

DNS servers (AD integrated) for each domain have entries for the servers in
that domain

 

If I do a reverse lookup from a machine that is pointed to the "right" DNS
server it works, otherwise I get a non-existent domain.  Hw do you solve
this?  Do you manually put in PTR records for all the servers in the
opposite domain?

 

Example:

Server1.corp.local is at 10.1.1.10

 

Server2.division.local is at 10.1.1.20

 

Client1.corp.local is at 10.100.100.100 with DNS server pointed to
DNSserver.corp.local

Client2.division.local is at 10.200.200.200 with DNS server pointed to
DNSserver.division.local

 

nslookup from client1 for 10.1.1.10 returns Server1

nslookup from client1 for 10.1.1.20 returns non-existent domain

 

nslookup from Client2 for 10.1.1.10 returns non-existent domain

nslookup from Client2 for 10.1.1.20 returns Server2

 

nslookup by name (forward lookup) works everywhere.

 

Brian Webb - MCSE
TDS Corporate IS, Windows Server Platform Team
Senior Systems Administrator

"When stuck on a problem as often can be, try to remember G.B.T.T.D. (Go
Back To The Definition)". - Dave Seybold

 

 

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~