Help on a dns issue. Please.

Archived from groups: microsoft.public.win2000.dns (More info?)

Ok try to make this quick, we are a school district. we
have 26 schools. each school has one win2k or 2k3 sevrer.
every computers is set up as its own dns server. They all
have internal ips and are working just fine. The problem
is they are not all showing up in network places so i cant
access them. this becomes a problem when im try to push
out updates to them.

Should i have them all acting as dns servers and point
them to our main dns server here at the main office. i
need to be able to see and access all of them. i can
terminal into them no problem. They just arent showing up.
not even sure if this is a result of dns.

Thanks
Chuck
7 answers Last reply
More about help issue please
  1. Archived from groups: microsoft.public.win2000.dns (More info?)

    In news:2901c01c46444$89ee0e10$a301280a@phx.gbl,
    Chuck Hake <chuckhake@eriesd.iu5.org> posted a question
    Then Kevin replied below:
    > Ok try to make this quick, we are a school district. we
    > have 26 schools. each school has one win2k or 2k3 sevrer.
    > every computers is set up as its own dns server. They all
    > have internal ips and are working just fine. The problem
    > is they are not all showing up in network places so i cant
    > access them. this becomes a problem when im try to push
    > out updates to them.
    >
    > Should i have them all acting as dns servers and point
    > them to our main dns server here at the main office. i
    > need to be able to see and access all of them. i can
    > terminal into them no problem. They just arent showing up.
    > not even sure if this is a result of dns.

    Network Places does _not_ use DNS, that is a NetBIOS function. NetBIOS is a
    broadcast protocol and will not cross between multiple subnets. You will
    need to set up WINS for Network Places to populate non-local machines.
    WINS is more reliable than just relying on NetBIOS broadcasts to populate
    Network Places.

    --
    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
    ==========================================
  2. Archived from groups: microsoft.public.win2000.dns (More info?)

    It could be that they aren't in the same IP subnet and
    that you are using the older down-rev mechanisms for
    browsing. It's set up to just keep the browser list
    within the subnet.

    Try using AD instead

    >-----Original Message-----
    >Ok try to make this quick, we are a school district. we
    >have 26 schools. each school has one win2k or 2k3 sevrer.
    >every computers is set up as its own dns server. They all
    >have internal ips and are working just fine. The problem
    >is they are not all showing up in network places so i
    cant
    >access them. this becomes a problem when im try to push
    >out updates to them.
    >
    >Should i have them all acting as dns servers and point
    >them to our main dns server here at the main office. i
    >need to be able to see and access all of them. i can
    >terminal into them no problem. They just arent showing
    up.
    >not even sure if this is a result of dns.
    >
    >Thanks
    >Chuck
    >.
    >
  3. Archived from groups: microsoft.public.win2000.dns (More info?)

    > Ok try to make this quick, we are a school district. we
    > have 26 schools. each school has one win2k or 2k3 sevrer.
    > every computers is set up as its own dns server. They all
    > have internal ips and are working just fine. The problem
    > is they are not all showing up in network places so i cant
    > access them. this becomes a problem when im try to push
    > out updates to them.
    >
    > Should i have them all acting as dns servers and point
    > them to our main dns server here at the main office. i
    > need to be able to see and access all of them. i can
    > terminal into them no problem. They just arent showing up.
    > not even sure if this is a result of dns.

    I'm assuming each school has its own DNS domain like
    e.g. school1, school2 and so on, if that's the case you'll
    only need to configure the different DNS servers to allow
    zone transfers to your central server, next you'll need to
    create each zone on your central DNS as a secondary
    zone and point the zone master to the relevant DNS of
    that particular school, this way you'll have a local copy
    of each zone which will be automatically updated (be
    sure also that each DNS has your central DNS IP in its
    notify list for the zone) everytime it changes and you'll
    probably solve your problem

    Regards
  4. Archived from groups: microsoft.public.win2000.dns (More info?)

    >-----Original Message-----
    >> Ok try to make this quick, we are a school district. we
    >> have 26 schools. each school has one win2k or 2k3
    sevrer.
    >> every computers is set up as its own dns server. They
    all
    >> have internal ips and are working just fine. The problem
    >> is they are not all showing up in network places so i
    cant
    >> access them. this becomes a problem when im try to push
    >> out updates to them.
    >>
    >> Should i have them all acting as dns servers and point
    >> them to our main dns server here at the main office. i
    >> need to be able to see and access all of them. i can
    >> terminal into them no problem. They just arent showing
    up.
    >> not even sure if this is a result of dns.
    >
    >I'm assuming each school has its own DNS domain like
    >e.g. school1, school2 and so on, if that's the case you'll
    >only need to configure the different DNS servers to allow
    >zone transfers to your central server, next you'll need to
    >create each zone on your central DNS as a secondary
    >zone and point the zone master to the relevant DNS of
    >that particular school, this way you'll have a local copy
    >of each zone which will be automatically updated (be
    >sure also that each DNS has your central DNS IP in its
    >notify list for the zone) everytime it changes and you'll
    >probably solve your problem
    >
    >Regards
    >
    >
    >
    >.
    >thanks alot the boss and i are going to try that in a few
    minutes.
  5. Archived from groups: microsoft.public.win2000.dns (More info?)

    In news:2901c01c46444$89ee0e10$a301280a@phx.gbl,
    Chuck Hake <chuckhake@eriesd.iu5.org> asked for help and I offered my
    suggestions below:
    > Ok try to make this quick, we are a school district. we
    > have 26 schools. each school has one win2k or 2k3 sevrer.
    > every computers is set up as its own dns server. They all
    > have internal ips and are working just fine. The problem
    > is they are not all showing up in network places so i cant
    > access them. this becomes a problem when im try to push
    > out updates to them.
    >
    > Should i have them all acting as dns servers and point
    > them to our main dns server here at the main office. i
    > need to be able to see and access all of them. i can
    > terminal into them no problem. They just arent showing up.
    > not even sure if this is a result of dns.
    >
    > Thanks
    > Chuck

    What sort of updates are you pushing? Hotfixes? If so, what are you using?
    SUS is pure IP and uses DNS for resolution to the SUS server if you set the
    URL in the GPO as an FQDN and not the NetBIOS name. As Kevin mentioned, the
    neighborhood is Browser Service based, which is NetBIOS based and has
    nothing to do with DNS. If you want full functionality for the neighborhood,
    use WINS for the infrastructure to insure NetBIOS resolution across the
    board. The Browser service will pick up all the names from WINS.

    As for DNS, Obiwan has a nice resolution.
    :-)

    --
    Regards,
    Ace

    Please direct all replies ONLY to the Microsoft public newsgroups
    so all can benefit.

    This posting is provided "AS-IS" with no warranties or guarantees
    and confers no rights.

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

    HAM AND EGGS: A day's work for a chicken;
    A lifetime commitment for a pig.
    --
    =================================
  6. Archived from groups: microsoft.public.win2000.dns (More info?)

    <snip>
    > What sort of updates are you pushing? Hotfixes? If so, what are you using?
    > SUS is pure IP and uses DNS for resolution to the SUS server if you set
    the
    > URL in the GPO as an FQDN and not the NetBIOS name. As Kevin mentioned,
    the
    > neighborhood is Browser Service based, which is NetBIOS based and has
    > nothing to do with DNS. If you want full functionality for the
    neighborhood,
    > use WINS for the infrastructure to insure NetBIOS resolution across the
    > board. The Browser service will pick up all the names from WINS.
    >
    > As for DNS, Obiwan has a nice resolution.
    > :-)

    Thanks Ace; just a note; an alternate solution if the issue is
    caused by "WINS" may be installing WINS on the central
    DNS machine, next setting up the remote DNS machines
    to act as WINS proxies and btw to point to the central DNS
    as their WINS server, the next step will be setting up all the
    remote clients to use their local DNS as WINS servers this
    way the WINS traffic will flow up to the central machine which
    will then keep the global database
  7. Archived from groups: microsoft.public.win2000.dns (More info?)

    In news:eXTnITQZEHA.1048@tk2msftngp13.phx.gbl,
    ObiWan <anzen.NO@SPAM.gmx.net> asked for help and I offered my suggestions
    below:
    > <snip>
    >> What sort of updates are you pushing? Hotfixes? If so, what are you
    >> using? SUS is pure IP and uses DNS for resolution to the SUS server
    >> if you set the URL in the GPO as an FQDN and not the NetBIOS name.
    >> As Kevin mentioned, the neighborhood is Browser Service based, which
    >> is NetBIOS based and has nothing to do with DNS. If you want full
    >> functionality for the neighborhood, use WINS for the infrastructure
    >> to insure NetBIOS resolution across the board. The Browser service
    >> will pick up all the names from WINS.
    >>
    >> As for DNS, Obiwan has a nice resolution.
    >> :-)
    >
    > Thanks Ace; just a note; an alternate solution if the issue is
    > caused by "WINS" may be installing WINS on the central
    > DNS machine, next setting up the remote DNS machines
    > to act as WINS proxies and btw to point to the central DNS
    > as their WINS server, the next step will be setting up all the
    > remote clients to use their local DNS as WINS servers this
    > way the WINS traffic will flow up to the central machine which
    > will then keep the global database

    Good point. On the DNS servers, set to use WINS resolution and supply IP of
    the central WINS server.

    To add, if there are mutliple WINS servers, use the central office as a
    "hub" and setup replication partners to and from it. If the partnerships are
    meshed, it will causes replication errors.

    --
    Regards,
    Ace

    Please direct all replies ONLY to the Microsoft public newsgroups
    so all can benefit.

    This posting is provided "AS-IS" with no warranties or guarantees
    and confers no rights.

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

    HAM AND EGGS: A day's work for a chicken;
    A lifetime commitment for a pig.
    --
    =================================
Ask a new question

Read More

DNS Server Microsoft DNS Windows