Re: FQDN - DNS resolution
From: ptwilliams (ptw2001_at_hotmail.com)
Date: 01/18/05
- Next message: Steve Ireland: "LDIFDE Import: userPassword returns blank"
- Previous message: Oleg A. Malahov: "Auto logon in Network Client for MS-DOS with AD"
- In reply to: Morag: "Re: FQDN - DNS resolution"
- Next in thread: ptwilliams: "Re: FQDN - DNS resolution"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 Jan 2005 12:26:48 -0000
No problem ;-)
-- Paul Williams http://www.msresource.net http://forums.msresource.net "Morag" <Morag@discussions.microsoft.com> wrote in message news:5ACE99B4-07E2-4DFE-8750-224FBC73C70F@microsoft.com... Thank you - that explanation was exactly what we needed. Morag "ptwilliams" wrote: > If you ping mydomain.co.uk you will get the IP address of one of the > records > that look like (same as parent folder) in the DNS console. > > If you only have one DC, this will always be the same. > > If you have multiple DCs in a single site this will be load-balanced, e.g. > the first is passed, then the second, etc. (from the server -the client > will > cache the first and use it again). > > If you have multiple DCs in multiple sites, you will get load-balencing > based on your subnet. So if you're in a remote site with two DCs and > there > are other DCs in other sites, clients in your site will get the first, > then > the second, then the first, etc. > > This is because the DNS server is using a feature called round-robin > (basic > load-balencing) and net-mask ordering (subnet prioritisation). > > Basically, when you ping the domain name you get a DC returned. You can > also connect to \\domain-name.co.uk (a Dfs referral), bind to the domain > using domain-name.co.uk (serverless bind), etc. > > Hope this helps, > > > -- > > Paul Williams > > http://www.msresource.net > http://forums.msresource.net > > > "Morag" <Morag@discussions.microsoft.com> wrote in message > news:EAA000C9-55C5-4C72-AAFE-4BDA3B2003D1@microsoft.com... > Can anyone tell me what result I should expect if I ping mydomain.co.uk - > the > IP address of any DC in the AD or specifically the IP address of the DC > that > is the PDC Emulator (Global Catalog/Bridgehead server at central site - I > am > located at the central site) ? > > "Herb Martin" wrote: > > > "Morag" <Morag@discussions.microsoft.com> wrote in message > > news:AB209474-62C1-4710-B88D-EDD15E6B9FA0@microsoft.com... > > > We are not having a problem with authentication or name resolution - > > > these > > > are both working corrrectly. If we ping machinename.mydomain.co.uk - > > > we > > get > > > the correct ip address. Nslookup shows we are using the correct local > > > DNS > > > server. > > > > > > We just want to understand what to expect if we ping mydomain.co.uk > > > (with > > > no host name. As I mentioned we get the IP address of one of the > > > remote > > site > > > DCs and not the PDC Emulator DC which is on our local site. > > > > All of the DCs register a name equal to their own (AD) domain. > > > > BTW, none of what you offered (despite common mistatements > > by just about everyone) are "FQDN". > > > > An FQDN is one that is terminated in a "." (DOT) and > > might be a zone name, or a machine name (which in DNS > > are also domain names again despite the common error > > of meaning a "dotted DNS name" instead of a FQDN.) > > > > These are a FQDN: www.microsoft.com. com. even "." > > > > These are not: www.microsoft.com microsoft.com etc > > > > -- > > Herb Martin > > > > > > "Morag" <Morag@discussions.microsoft.com> wrote in message > > news:AB209474-62C1-4710-B88D-EDD15E6B9FA0@microsoft.com... > > > We are not having a problem with authentication or name resolution - > > > these > > > are both working corrrectly. If we ping machinename.mydomain.co.uk - > > > we > > get > > > the correct ip address. Nslookup shows we are using the correct local > > > DNS > > > server. > > > > > > We just want to understand what to expect if we ping mydomain.co.uk > > > (with > > > no host name. As I mentioned we get the IP address of one of the > > > remote > > site > > > DCs and not the PDC Emulator DC which is on our local site. > > > > > > Thanks > > > "Desmond Lee" wrote: > > > > > > > If you do a ping FQDN_host_name, the request is directed to the > > host_name as > > > > recorded in DNS / WINS (or broadcast as the case may be). This is > > > > normal > > > > behavior and has nothing to do with AD. > > > > > > > > DNS is used by Win 2000 / XP to locate AD services such as a DC, > > > > Global > > > > Catalog, etc. Perhaps this is what you are looking for? In this > > > > case, > > > > provided that the AD Site design is properly setup (IP subnets > > > > mapped > > > > correctly), the phenomenon where a Win client gets authenticated by > > > > a > > > > DC > > in > > > > another site could happen. > > > > > > > > Do let us know if this helps. > > > > > > > > "Morag" wrote: > > > > > > > > > We have 2 sites. Local HQ and Remote site, both have 2 DCs (also > > > > > AD > > > > > Integrated DNS). > > > > > > > > > > If we "ping fqdn" (eg. ping mydomain.co.uk ) we get the IP address > > > > > of > > one of > > > > > the Remote Site DCs - we expected to get the IP address of one of > > > > > the > > local > > > > > DCs (which is the PDC Emulator). > > > > > > > > > > What should the domain resolve as - the PDC emulator or any DC in > > > > > the > > domain ? > > > > > > > > >
- Next message: Steve Ireland: "LDIFDE Import: userPassword returns blank"
- Previous message: Oleg A. Malahov: "Auto logon in Network Client for MS-DOS with AD"
- In reply to: Morag: "Re: FQDN - DNS resolution"
- Next in thread: ptwilliams: "Re: FQDN - DNS resolution"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading