close

Privacy guaranteed - Your email is not shared with anyone.

Welcome to Glock Talk

Why should YOU join our Glock forum?

  • Converse with other Glock Enthusiasts
  • Learn about the latest hunting products
  • Becoming a member is FREE and EASY

If you consider yourself a beginner or an avid shooter, the Glock Talk community is your place to discuss self defense, concealed carry, reloading, target shooting, and all things Glock.

DNS Scavenging

Discussion in 'Tech Talk' started by MavsX, Jun 9, 2010.

  1. MavsX

    MavsX The Dude Abides

    3,033
    0
    Jan 19, 2009
    Arlington, VA
    Anybody know anything about DNS Scavenging? We are having some real problems here at work with DNS being wrong. I've heard that if you botch it, it can really funk up active directory. So I'm hesitant to do anything. Any ideas?
     
    Last edited: Jun 9, 2010
  2. Linux3

    Linux3

    1,399
    0
    Dec 31, 2008

  3. MavsX

    MavsX The Dude Abides

    3,033
    0
    Jan 19, 2009
    Arlington, VA
    thanks L3 for the link. I'm going to start reviewing this and seeing what i can get done.
     
  4. KevinFACE

    KevinFACE

    1,154
    2
    Feb 16, 2010
    AD and Exchange are HEAVILY reliant on DNS, if you screw it up.. you WILL have problems, flat out.. no ifs ands or buts.

    I highly suggest you plan before acting.
     
  5. KharToon

    KharToon

    969
    0
    Nov 2, 2007
  6. MavsX

    MavsX The Dude Abides

    3,033
    0
    Jan 19, 2009
    Arlington, VA
    dns remembers everything. can't remote in to workstations sometimes because dns thinks the machines are in the wrong subnet, etc.
     
  7. KharToon

    KharToon

    969
    0
    Nov 2, 2007
    Are you the windows admin? Is this happening from every workstation?

    First thing I would check is that the dc is pointed to itself for DNS in tcp/ip

    Then make sure that all networks that are in use are tied to an ad site.

    Then clear the dns cache on the dns server

    Then clear the cache on the workstations
     
  8. RTmarc

    RTmarc

    69
    0
    Mar 18, 2008
    Birmingham, AL
    Enable scavenging and set to 7 days. It's not as big of a deal as some people are trying to make it. Just make sure that your DCs and Exchange servers are using static IPs. If you feel so inclined, add static DNS entries for sensitive servers.
     
    Last edited: Jun 16, 2010
  9. MavsX

    MavsX The Dude Abides

    3,033
    0
    Jan 19, 2009
    Arlington, VA
    for the most part our workstations stay put where they are supposed to be. all servers are statics. Sometimes i have to bring a computer into the tech bench which is in a different subnet that the workstation subnets. dns remembers all. Which, once i throw the new computer or whatever back into the original subnet then i have 2 entries for the same machine, and then i can't do anything remote wise to it.

    i has helped to go into the dns lookup zones and manually delete the objects. But, it;s just a pain in the ass.

    luckily most of our machines don;t move too much.