Questions

Im sure its dns issues

+
0 Votes
Locked

Im sure its dns issues

Tash
Hey guys
I have a questions about my dns.
Im running server 2003 and hosting my own website on this server. running 2pcs with xp pro and 1 laptop with vista business. my problem is that if im on my server i can go to www.mywebsite.com, but on any work stations xp or vista i can not go to www.mywebsite.com . i can use the servers ip and it will work with no issues. what gives? i know i can go to the host file and add the info there and it works but i do not want it this way. my vista laptop is on a wireless router and the wireless is connected to my symantec firewall router as a AP only. i also have an iphone and i have exchange working on that. but it has the same issue that the other computers have. so i know its has to be my dns on the server. right?
  • +
    0 Votes
    seanferd

    Is the domain configured to be resolved locally? If so, make sure the A, CNAME, MX records are configured.

    Is this an internet registered domain name? If so: Are requests properly forwarded to an internet DNS server? Have records had time to propagate from the authoritative nameserver? (Could be several days.)

    +
    0 Votes

    dns

    Tash

    HMMMM good question im certain i went threw the process of configuring it but i will look into that and see what i find.

    Thank you

    +
    0 Votes
    Nimmo

    One a workstation and the server do an IP config /all and compare results. Where is you local DNS located i.e. server, router.

    Make sure the workstations have the correct gateway set & DNS servers.

    +
    0 Votes
    El_Duce

    sometimes it just won't work because of cache

    on the workstations, go to start en then run. type "cmd" (without quotes) and hit enter.
    Type "ipconfig /flushdns" (without quotes) and hit enter

    retry going to your site

    +
    0 Votes
    jtakiwi

    Question 1 - Are you using "mycompany.com" as the internal domain name? As in .com instead of .local or something non public?

    Q2 - If you are not using .com for internal domain, you need to add a .com forward lookup zone in dns, then add your A record to that zone.

    +
    0 Votes
    Nimmo

    You don't add the external domain into the local forward lookup zone; you add it into your external zone record in your service providers DNS servers.

    But that's not the problem anyway seen as the server is accessing the site via hostname.

    As per my suggest above do an IP config and check the DNS on the workstations it sounds to me like your workstations are not getting the correct DNS addresses seen as the server can resolve but not the workstations.

    If El_Duce's suggestion of doing a /flushdns doesn't work do an IP config /release then /renew then check the TCP/IP details again.

    If it has the wrong DNS addresses check your DHCP server is sending the correct DNS out to the workstations.

    +
    0 Votes
    Tash

    hello
    I noticed on my server and i should have told this from the start. im using acronyms for my local server name but my registered domain name is the full name of my company so i guess is how do i setup a new reverse or foward record?

    +
    0 Votes
    Tash

    hello
    I noticed on my server and i should have told this from the start. im using acronyms for my local server name (.local) but my registered domain name is the full name of my company (.com) so i guess is how do i setup a new reverse or foward record?

    +
    0 Votes

    DNS

    Nimmo

    That's how it should be because your local domain name is just that local it doesn't get seen on the internet.

    (You can actually call it anything you like but using the .local is recommended).

    As I mentioned before you don't put your external DNS into your forward lookup zone because again your local DNS is just that local.

    You put your external records for example (A record of remote.domain.com which you may use to remotely connect to your terminal server or a MX record of mail.domain.com which points to your mail server). Both of which point to your external IP address of your organization.

    You then need to create rules to forward these requests to the appropriate internet addresses. For example you may have a rule stating that only certain IP addresses are allowed to connect to your SMTP server on address 10.0.0.x.

    None of this is the issue because your server is able to resolve but not the workstations so it's a local configuration issue.

    Have you checked the TCP/IP setting on each workstation to confirm that they are using the correct DNS server (your servers address) and also check to make sure that the DHCP server is sending the right DNS configuration (the servers IP address) to the clients.

    +
    0 Votes

    dns

    Tash

    im using 2 nics 192.x.x.x for my server
    10.x.x.x and my external.
    My dchp server is sending out the correct ip (192.x.x.x) all workstations/iphone are recieving ip 192.x.x.x and they are all pointing to my server (192.x.x.x) but no workstaions are pointing to a 10. base ip. witch im sure its not supposed to.

    +
    0 Votes

    DNS

    Nimmo

    Correct me if I'm wrong but is you setup as follows:

    Internet -- router -- 10.x.x.x -- server -- 192.x.x.x -- internal LAN.

    Are you using any firewall software such as ISA on the server?

    +
    0 Votes

    dns

    Tash

    Your correct im using what you have posted. I am not using ISA (not yet but will one day)
    Once i fix and understand more clearly my issue i will use ISA.
    just want to say thanks again for helping me out with this issue.

    +
    0 Votes

    DNS

    Nimmo

    No problem, basically what you can do in the mean time is to setup RRAS on your server (which you will need to do if your going to put ISA on it anyway).

    I've found this link that should help you out http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Server-2003-act-NAT-router.html

  • +
    0 Votes
    seanferd

    Is the domain configured to be resolved locally? If so, make sure the A, CNAME, MX records are configured.

    Is this an internet registered domain name? If so: Are requests properly forwarded to an internet DNS server? Have records had time to propagate from the authoritative nameserver? (Could be several days.)

    +
    0 Votes

    dns

    Tash

    HMMMM good question im certain i went threw the process of configuring it but i will look into that and see what i find.

    Thank you

    +
    0 Votes
    Nimmo

    One a workstation and the server do an IP config /all and compare results. Where is you local DNS located i.e. server, router.

    Make sure the workstations have the correct gateway set & DNS servers.

    +
    0 Votes
    El_Duce

    sometimes it just won't work because of cache

    on the workstations, go to start en then run. type "cmd" (without quotes) and hit enter.
    Type "ipconfig /flushdns" (without quotes) and hit enter

    retry going to your site

    +
    0 Votes
    jtakiwi

    Question 1 - Are you using "mycompany.com" as the internal domain name? As in .com instead of .local or something non public?

    Q2 - If you are not using .com for internal domain, you need to add a .com forward lookup zone in dns, then add your A record to that zone.

    +
    0 Votes
    Nimmo

    You don't add the external domain into the local forward lookup zone; you add it into your external zone record in your service providers DNS servers.

    But that's not the problem anyway seen as the server is accessing the site via hostname.

    As per my suggest above do an IP config and check the DNS on the workstations it sounds to me like your workstations are not getting the correct DNS addresses seen as the server can resolve but not the workstations.

    If El_Duce's suggestion of doing a /flushdns doesn't work do an IP config /release then /renew then check the TCP/IP details again.

    If it has the wrong DNS addresses check your DHCP server is sending the correct DNS out to the workstations.

    +
    0 Votes
    Tash

    hello
    I noticed on my server and i should have told this from the start. im using acronyms for my local server name but my registered domain name is the full name of my company so i guess is how do i setup a new reverse or foward record?

    +
    0 Votes
    Tash

    hello
    I noticed on my server and i should have told this from the start. im using acronyms for my local server name (.local) but my registered domain name is the full name of my company (.com) so i guess is how do i setup a new reverse or foward record?

    +
    0 Votes

    DNS

    Nimmo

    That's how it should be because your local domain name is just that local it doesn't get seen on the internet.

    (You can actually call it anything you like but using the .local is recommended).

    As I mentioned before you don't put your external DNS into your forward lookup zone because again your local DNS is just that local.

    You put your external records for example (A record of remote.domain.com which you may use to remotely connect to your terminal server or a MX record of mail.domain.com which points to your mail server). Both of which point to your external IP address of your organization.

    You then need to create rules to forward these requests to the appropriate internet addresses. For example you may have a rule stating that only certain IP addresses are allowed to connect to your SMTP server on address 10.0.0.x.

    None of this is the issue because your server is able to resolve but not the workstations so it's a local configuration issue.

    Have you checked the TCP/IP setting on each workstation to confirm that they are using the correct DNS server (your servers address) and also check to make sure that the DHCP server is sending the right DNS configuration (the servers IP address) to the clients.

    +
    0 Votes

    dns

    Tash

    im using 2 nics 192.x.x.x for my server
    10.x.x.x and my external.
    My dchp server is sending out the correct ip (192.x.x.x) all workstations/iphone are recieving ip 192.x.x.x and they are all pointing to my server (192.x.x.x) but no workstaions are pointing to a 10. base ip. witch im sure its not supposed to.

    +
    0 Votes

    DNS

    Nimmo

    Correct me if I'm wrong but is you setup as follows:

    Internet -- router -- 10.x.x.x -- server -- 192.x.x.x -- internal LAN.

    Are you using any firewall software such as ISA on the server?

    +
    0 Votes

    dns

    Tash

    Your correct im using what you have posted. I am not using ISA (not yet but will one day)
    Once i fix and understand more clearly my issue i will use ISA.
    just want to say thanks again for helping me out with this issue.

    +
    0 Votes

    DNS

    Nimmo

    No problem, basically what you can do in the mean time is to setup RRAS on your server (which you will need to do if your going to put ISA on it anyway).

    I've found this link that should help you out http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Server-2003-act-NAT-router.html