1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

DNS Problems after IP address change

Discussion in 'Networking (Hardware & Software)' started by adamt56, 2005/07/21.

Thread Status:
Not open for further replies.
  1. 2005/07/21
    adamt56

    adamt56 Inactive Thread Starter

    Joined:
    2005/03/24
    Messages:
    38
    Likes Received:
    0
    I am currently unable to access any of my internally hosted websites from within my network.

    This occured after changing IP addresses.

    I can get to them fine from outside of my domain.

    Mabye I am missing something simple, but does anyone have any ideas here?

    Thanks,

    Adam T.
     
  2. 2005/07/21
    Scott Smith

    Scott Smith Inactive Alumni

    Joined:
    2002/01/12
    Messages:
    1,950
    Likes Received:
    4
    Please explain further.
     

  3. to hide this advert.

  4. 2005/07/21
    adamt56

    adamt56 Inactive Thread Starter

    Joined:
    2005/03/24
    Messages:
    38
    Likes Received:
    0
    The IP address of my WAN link changed. As a result, I had to make a change in DNS to point my domains, to my Public IP address.

    I can access the sites fine from outside of my network, same DNS server.

    Boggling my mind for the moment.
     
  5. 2005/07/22
    NetDoc

    NetDoc Inactive

    Joined:
    2005/01/09
    Messages:
    215
    Likes Received:
    0
    Two quick checks.

    Can you ping the address (not name) that you want to access?

    Did you modify DHCP to assign a new DNS address?

    DRD
     
    Last edited: 2005/07/22
  6. 2005/07/22
    adamt56

    adamt56 Inactive Thread Starter

    Joined:
    2005/03/24
    Messages:
    38
    Likes Received:
    0
    Ok, I solved the issue last night.

    I have an internal DNS server here which isn't really used much, but is a must have since I am running Active Directory.

    I have all clients on my network pulling external DNS server addresses.

    I just set my internal DNS server as the primary DNS server and this fixed everything.

    It's interesting though, I can go back to using public DNS servers and NO internal DNS servers and hit all my websites with no problem now.
     
  7. 2005/07/22
    Scott Smith

    Scott Smith Inactive Alumni

    Joined:
    2002/01/12
    Messages:
    1,950
    Likes Received:
    4
    I'll bet the logons are quicker now too. ;)


    Your Internal DNS needs to know about your Domains.
    Alias records need to be created in DNS so he can find local websites.
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.