Re: Network Problems and DNS

From: Kevin D. Goodknecht [MVP] (admin_at_nospam.LSAOL.COM)
Date: 04/05/04


Date: Mon, 5 Apr 2004 18:17:37 -0500

In news:O%23iibS0GEHA.2576@TK2MSFTNGP11.phx.gbl,
Robert Cohen <dont@want.spam.com> posted a question
Then Kevin replied below:
> btw, what is 127.0.0.1. I noticed it listed as the DNS server for a
> lot of the PPP stuff. I can ping it but I assume that is not an
> internal IP address. Is that a correct entry or did it get in their
> somehow? Just trying to understand.
>
Actually the 127.0.0.1 is part of the problem, it is the DNS address on the
dial in adapter. This adapter will configure itself . What you can do is
configure the listener address on the DNS server (interfaces tab) to listen
only on 10.0.0.2 then disable and re-enable the Dial in adapter, IIRC that
will cause the dial in to adopt 10.0.0.2 as its DNS server and keep DNS from
trying to register the 192.168.234.235 record.
Another problem with multihomed DCs is all the Blank (same as parent folder)
records, DC's will automatically try to create a blank record for each IP
address on the DC. In truth the only blank record you should have it for the
adapter that is at the top of the binding order and has file sharing bound.

But I see a big problem,
DNS test . . . . . . . . . . . . . : Passed
      Interface {C2996A6A-0D4E-44DA-AE5D-42C633427EAF}<--Default adapter
        DNS Domain:
        DNS Servers: 10.0.0.2 10.0.0.3
        IP Address: 10.1.0.2
        Expected registration with PDN (primary DNS domain name):
          Hostname: bbh01.baltimorebehavioralhealth.org.
          Authoritative zone: baltimorebehavioralhealth.org.
          Primary DNS server: bbh01.baltimorebehavioralhealth.org 10.0.0.2
          Authoritative NS:10.1.0.10 10.0.0.2 10.0.0.9 10.0.0.3
      Interface {EC320E1B-7263-401F-9D72-D1D93918D38C}
        DNS Domain:
        DNS Servers: 10.0.0.2 10.0.0.3
        IP Address: 10.0.0.2 63.141.72.67<---This interface has IP addresses
on different subnets, one of which is a public address. The problem with
this is if you bind file sharing to this you are binding file sharing to a
publicly available interface. Not good!

What interface is upposed to be your private internal interface?
That is the interface that should have its addresses registered in DNS, it
should also have file sharing enabled on it.

        Expected registration with PDN (primary DNS domain name):
          Hostname: bbh01.baltimorebehavioralhealth.org.
          Authoritative zone: baltimorebehavioralhealth.org.
          Primary DNS server: bbh01.baltimorebehavioralhealth.org 10.0.0.2
          Authoritative NS:10.1.0.10 10.0.0.2 10.0.0.9 10.0.0.3
      Interface {B47C4124-6D9C-4768-AF33-9574AA936399}
        DNS Domain:
        DNS Servers: 127.0.0.1
        IP Address: 192.168.234.235
        Expected registration with PDN (primary DNS domain name):
          Hostname: bbh01.baltimorebehavioralhealth.org.
          Authoritative zone: baltimorebehavioralhealth.org.
          Primary DNS server: bbh01.baltimorebehavioralhealth.org 10.0.0.2
          Authoritative NS:10.1.0.10 10.0.0.2 10.0.0.9 10.0.0.3
      Verify DNS registration:
        Name: bbh01.baltimorebehavioralhealth.org
        Expected IP: 10.1.0.2 10.0.0.2 192.168.234.235
          Server 10.1.0.10: ERROR_NO_MATCH
            Missing IP from DNS: 10.1.0.2 192.168.234.235
          Server 10.0.0.2: ERROR_NO_MATCH
            Missing IP from DNS: 10.1.0.2 192.168.234.235
          Server 10.0.0.9: Error 1460 ERROR_TIMEOUT
          Server 10.0.0.3: NO_ERROR
              [WARNING]: The DNS registration for
'bbh01.baltimorebehavioralhealth.org' is correct only on some DNS servers.
                   Please wait 15 min for replication and run the test
again.
Check the DNS registration for DCs entries on DNS server '10.0.0.2'
The Record is different on DNS server '10.0.0.2'.
DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.
Your DC entry is one of them on DNS server '10.0.0.2', no need to
re-register.

-- 
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.
==========================================
 http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
 http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
 http://www.oehelp.com/OEBackup/Default.aspx
==========================================


Relevant Pages

  • Re: DNS problems going out
    ... > You enable the DNS server on both interfaces from the DNS Server ... > between your LAN and the Internet? ... > 2) Do you have a valid IP address on the external interface? ... >> Original Client IP Client Agent Authenticated Client Service Server Name ...
    (microsoft.public.isa)
  • Re: DNS problems going out
    ... You enable the DNS server on both interfaces from the DNS Server management ... between your LAN and the Internet? ... Do you have a valid IP address on the external interface? ... > Original Client IP Client Agent Authenticated Client Service Server Name ...
    (microsoft.public.isa)
  • Re: trouble with dynamic IP and dyndns host
    ... | Router PIX501 with os 3.7 ... | DynDNS hostname: myhost.dyndns.org ... | From outside interface I can access all the services with no trouble. ... Perhaps you can set a dns server value in your PIX and set bidirectional ...
    (comp.dcom.sys.cisco)
  • Re: Multihomed domain.
    ... I tried changing the dns server for 192.168.1.1 for both interfaces, ... OpenVPN, the reason for it, is that we need all the traffic to be ... encrypted into the OpenVPN NIC interface. ... I'm not quite sure too how OpenVPN works for its encryption, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Network Problems and DNS
    ... > will cause the dial in to adopt 10.0.0.2 as its DNS server and keep DNS ... > this is if you bind file sharing to this you are binding file sharing to a ... > publicly available interface. ...
    (microsoft.public.windows.server.dns)