How Windows 2003 Secondary Zone works?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Can someone help me to understand how 2ndary zone works under Windows 2003
My Wndows 2003 (my.local) VPN to my customer's (customer.local) LAN. Customer has Widows 2000. No WINS on either side
I want be able to ping all customer's PC by name. Here's what I did

On customer side
-On DNS, customer, properties, security, add, Everyone
-Under forward lookup zone, properties, zone transfer, check 'Allow Zone Transfers', select only to server (my DNS IP
On my side
Under DNS, Forward Lookup Zone, add secondary zone, name: customer.loca

I did get all the DNS records from customer's dns. But when I ping the PC's name, I cannot get name resolution
I use ping pcname, ping customer.pcname, or customer.local.pcname, none works

Jimmy
 
In
jimmy Chang said:
Can someone help me to understand how 2ndary zone works under
Windows 2003?
My Wndows 2003 (my.local) VPN to my customer's (customer.local) LAN.
Customer has Widows 2000. No WINS on either side. I want be able to
ping all customer's PC by name. Here's what I did:

On customer side:
-On DNS, customer, properties, security, add, Everyone.
-Under forward lookup zone, properties, zone transfer, check 'Allow
Zone Transfers', select only to server (my DNS IP) On my side:
Under DNS, Forward Lookup Zone, add secondary zone, name:
customer.local

I did get all the DNS records from customer's dns. But when I ping
the PC's name, I cannot get name resolution.
I use ping pcname, ping customer.pcname, or customer.local.pcname,
none works.

Jimmy
Click to expand...
What happens if you ping pcname.customer.local which would be the correct
FQDN?
If you want to ping by just pcname you have to add customer.local the DNS
search list on the DNS tab in TCP/IP properties.
 
In
Kevin D. Goodknecht said:
In
What happens if you ping pcname.customer.local which would be the
correct FQDN?
If you want to ping by just pcname you have to add customer.local the
DNS search list on the DNS tab in TCP/IP properties.


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
Click to expand...

Kevin,
There could be a boatload more factors going on here too that would affect
this that we need more info, such as:

1. Are the clients and vendor's subnets NATted?
2. If so, has the necessary port remaps been done?
3. On top of that, is there a firewall or proxy on either side that would
complicate if a bit more?
4. Pinging the private IPs won't help, unless there's a VPN between the two
subnets, which actually is something I would rather see for this scenario
due to security.

:-)


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Jimmy Chang said:
I got it, sorry I did not read the answer. It work perfectly. Thanks!
Click to expand...

Good to hear.
:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top