| Author |
Message |
grmickelson
Guest
|
 Posted:
Sun Jan 23, 2005 6:45 am Post subject:
DNS Server is not working |
|
|
I need some help in what and how to configure my DNS. I am running Server
2003 SBS.
I current have DNS Configured.
Local name is SYSCONDC01.SYSCONRESOURCES.LOCAL ip 192.168.1.10
I am also trying to set up my Domain name to also work which is
SYSCONRESOURCES.COM. ip 68.147.209.152
I need help in setting up the forwarding settings as everything I do does
not work and I cannot get to my machine from the internet. I would like to
use my machine as the DNS providor for my domain (I hope I got the wording
correct) but I am lost. I have had myt Nephew help (he works on a large
server setup) but he has not been able to get it to work as well.
All I am really looking for is the setting/entries I need .
Note: at the provider of the domain name we have setup the Name server to
point to server.sysconresources.com
Glenn |
|
| Back to top |
|
 |
Herb Martin
Guest
|
| Posted:
Sun Jan 23, 2005 6:45 am Post subject:
Re: DNS Server is not working |
|
|
"grmickelson" <grmickelson@discussions.microsoft.com> wrote in message
news:730C22F1-CD88-49B7-A04C-541316D77E1E@microsoft.com...
| Quote: | I need some help in what and how to configure my DNS. I am running Server
2003 SBS.
I current have DNS Configured.
Local name is SYSCONDC01.SYSCONRESOURCES.LOCAL ip 192.168.1.10
I am also trying to set up my Domain name to also work which is
SYSCONRESOURCES.COM. ip 68.147.209.152
|
Ok, since they are two different names you just make
two different zones if you want to hold them both on the
same DNS server machine(s).
| Quote: | I need help in setting up the forwarding settings as everything I do does
not work and I cannot get to my machine from the internet. I would like
to
use my machine as the DNS providor for my domain (I hope I got the wording
correct) but I am lost.
|
That's close enough, but (trust me) you do NOT want
to try to provide your own PUBLIC DNS server to
support that public name (SysConResource.Com).
That is MUCH better left at your Registrar where they
have multiple servers, 24/7 staff, fault tolerant hardware
etc.
Also, in any case you want to MENTALLY distinguish
between providing resolution for your OWN resources
(like above) to others, and for helping your users resolve
ALL names, both public and private.
They are really two different jobs, but most people new
to DNS miss this distinction since it is common for the
same DNS server to (end up having to) do both.
For YOUR users do it this way:
Set the INTERNAL computers to use ONLY your
internal DNS server (in their NIC->IP properties)
This will ensure they can resolve all internal names
BUT it might give them trouble with External (Internet)
names unless you setup forwarding correctly.
Set the INTERNAL DNS server to forward to the ISP
DNS server that your machine WOULD have used
if it didn't have a DNS server (and probably receives
from the DHCP if you use dial, cable, or DSL.
Here's a likely TRAP IF your server is also your router
to the Internet (if it isn't you can still use the idea to find
the correct ISP DNS for forwarding):
If that machine is a router it likely receives it's DNS
setting for the external NIC from DHCP (i.e., from
the ISP) and even your DC/Server itself must be
set STRICTLY to use only internal (itself) DNS
servers. (Remember we are going to forward to
handle the outside names.)
So, on that external NIC, find the setting for DNS server,
and WRITE IT DOWN. Then remove it, by overtyping
the value with again it's OWN address.
Now, you wrote down that external ISP DNS address, right?
THAT address is what you put in for the forwarder.
| Quote: | I have had myt Nephew help (he works on a large
server setup) but he has not been able to get it to work as well.
All I am really looking for is the setting/entries I need .
Note: at the provider of the domain name we have setup the Name server to
point to server.sysconresources.com
|
Doesn't the provider give you the option of leaving the
DNS with them and using a web form to handle EXTERNAL
DNS name resolution?
If they do, use it. Otherwise consider changing to GoDaddy
or another big provider with this service.
--
Herb Martin
|
|
| Back to top |
|
|
grmickelson
Guest
|
| Posted:
Sun Jan 23, 2005 9:57 pm Post subject:
Re: DNS Server is not working |
|
|
You convinced me. I have reset the settings with provider to leave the DNS
with them as well as to turn on forwarding to my machine. Now to wait 24-48
hours to see if all is working.
Glenn
"Herb Martin" wrote:
| Quote: | "grmickelson" <grmickelson@discussions.microsoft.com> wrote in message
news:730C22F1-CD88-49B7-A04C-541316D77E1E@microsoft.com...
I need some help in what and how to configure my DNS. I am running Server
2003 SBS.
I current have DNS Configured.
Local name is SYSCONDC01.SYSCONRESOURCES.LOCAL ip 192.168.1.10
I am also trying to set up my Domain name to also work which is
SYSCONRESOURCES.COM. ip 68.147.209.152
Ok, since they are two different names you just make
two different zones if you want to hold them both on the
same DNS server machine(s).
I need help in setting up the forwarding settings as everything I do does
not work and I cannot get to my machine from the internet. I would like
to
use my machine as the DNS providor for my domain (I hope I got the wording
correct) but I am lost.
That's close enough, but (trust me) you do NOT want
to try to provide your own PUBLIC DNS server to
support that public name (SysConResource.Com).
That is MUCH better left at your Registrar where they
have multiple servers, 24/7 staff, fault tolerant hardware
etc.
Also, in any case you want to MENTALLY distinguish
between providing resolution for your OWN resources
(like above) to others, and for helping your users resolve
ALL names, both public and private.
They are really two different jobs, but most people new
to DNS miss this distinction since it is common for the
same DNS server to (end up having to) do both.
For YOUR users do it this way:
Set the INTERNAL computers to use ONLY your
internal DNS server (in their NIC->IP properties)
This will ensure they can resolve all internal names
BUT it might give them trouble with External (Internet)
names unless you setup forwarding correctly.
Set the INTERNAL DNS server to forward to the ISP
DNS server that your machine WOULD have used
if it didn't have a DNS server (and probably receives
from the DHCP if you use dial, cable, or DSL.
Here's a likely TRAP IF your server is also your router
to the Internet (if it isn't you can still use the idea to find
the correct ISP DNS for forwarding):
If that machine is a router it likely receives it's DNS
setting for the external NIC from DHCP (i.e., from
the ISP) and even your DC/Server itself must be
set STRICTLY to use only internal (itself) DNS
servers. (Remember we are going to forward to
handle the outside names.)
So, on that external NIC, find the setting for DNS server,
and WRITE IT DOWN. Then remove it, by overtyping
the value with again it's OWN address.
Now, you wrote down that external ISP DNS address, right?
THAT address is what you put in for the forwarder.
I have had myt Nephew help (he works on a large
server setup) but he has not been able to get it to work as well.
All I am really looking for is the setting/entries I need .
Note: at the provider of the domain name we have setup the Name server to
point to server.sysconresources.com
Doesn't the provider give you the option of leaving the
DNS with them and using a web form to handle EXTERNAL
DNS name resolution?
If they do, use it. Otherwise consider changing to GoDaddy
or another big provider with this service.
--
Herb Martin
Glenn
|
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Mon Jan 24, 2005 2:00 am Post subject:
Re: DNS Server is not working |
|
|
"grmickelson" <grmickelson@discussions.microsoft.com> wrote in message
news:CF8D3D7E-B99A-4215-9E08-BCA5CD19D839@microsoft.com...
| Quote: | You convinced me. I have reset the settings with provider to leave the
DNS
with them as well as to turn on forwarding to my machine. Now to wait
24-48
hours to see if all is working.
|
Is this the ISP that has the DNS now?
That is not my first choice, but even that is usually
preferable to doing it yourself IF they have an interface
that let's you make your own changes.
(Almost) all of the big registrars that provide DNS
services now seem to have that.
IF it works well for you then go with them. Otherwise
look at getting to a big registrar that GIVE YOU control
of the records.
You will change ISPs more often (over the years) than
you will need to change registrars.
--
Herb Martin
| Quote: | Glenn
"Herb Martin" wrote:
"grmickelson" <grmickelson@discussions.microsoft.com> wrote in message
news:730C22F1-CD88-49B7-A04C-541316D77E1E@microsoft.com...
I need some help in what and how to configure my DNS. I am running
Server
2003 SBS.
I current have DNS Configured.
Local name is SYSCONDC01.SYSCONRESOURCES.LOCAL ip 192.168.1.10
I am also trying to set up my Domain name to also work which is
SYSCONRESOURCES.COM. ip 68.147.209.152
Ok, since they are two different names you just make
two different zones if you want to hold them both on the
same DNS server machine(s).
I need help in setting up the forwarding settings as everything I do
does
not work and I cannot get to my machine from the internet. I would
like
to
use my machine as the DNS providor for my domain (I hope I got the
wording
correct) but I am lost.
That's close enough, but (trust me) you do NOT want
to try to provide your own PUBLIC DNS server to
support that public name (SysConResource.Com).
That is MUCH better left at your Registrar where they
have multiple servers, 24/7 staff, fault tolerant hardware
etc.
Also, in any case you want to MENTALLY distinguish
between providing resolution for your OWN resources
(like above) to others, and for helping your users resolve
ALL names, both public and private.
They are really two different jobs, but most people new
to DNS miss this distinction since it is common for the
same DNS server to (end up having to) do both.
For YOUR users do it this way:
Set the INTERNAL computers to use ONLY your
internal DNS server (in their NIC->IP properties)
This will ensure they can resolve all internal names
BUT it might give them trouble with External (Internet)
names unless you setup forwarding correctly.
Set the INTERNAL DNS server to forward to the ISP
DNS server that your machine WOULD have used
if it didn't have a DNS server (and probably receives
from the DHCP if you use dial, cable, or DSL.
Here's a likely TRAP IF your server is also your router
to the Internet (if it isn't you can still use the idea to find
the correct ISP DNS for forwarding):
If that machine is a router it likely receives it's DNS
setting for the external NIC from DHCP (i.e., from
the ISP) and even your DC/Server itself must be
set STRICTLY to use only internal (itself) DNS
servers. (Remember we are going to forward to
handle the outside names.)
So, on that external NIC, find the setting for DNS server,
and WRITE IT DOWN. Then remove it, by overtyping
the value with again it's OWN address.
Now, you wrote down that external ISP DNS address, right?
THAT address is what you put in for the forwarder.
I have had myt Nephew help (he works on a large
server setup) but he has not been able to get it to work as well.
All I am really looking for is the setting/entries I need .
Note: at the provider of the domain name we have setup the Name server
to
point to server.sysconresources.com
Doesn't the provider give you the option of leaving the
DNS with them and using a web form to handle EXTERNAL
DNS name resolution?
If they do, use it. Otherwise consider changing to GoDaddy
or another big provider with this service.
--
Herb Martin
Glenn
|
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Mon Jan 24, 2005 2:04 am Post subject:
Re: DNS Server is not working |
|
|
"grmickelson" <grmickelson@discussions.microsoft.com> wrote in message
news:CF8D3D7E-B99A-4215-9E08-BCA5CD19D839@microsoft.com...
| Quote: | You convinced me. I have reset the settings with provider to leave the
DNS
with them as well as to turn on forwarding to my machine. Now to wait
24-48
hours to see if all is working.
|
YOUR resolution (for the Internet) should work immediately.
The world finding your SITE will not work until the PARENT
(.com) is updated to point to the correct DNS servers AND those
DNS servers have the correct values for your resources (Web
site, etc.)
The reason for that delay is that if I wish to visit your site,
I must go to the ROOT (".", or dot, zone), find the last tag,
(e.g., ".com"), then find your DNS servers (wherever they
might be, even in another zone) and then from those DNS
servers find your Web site A-host record.
It only takes a moment but if the chain is broken it will
not work correctly.
--
Herb Martin
| Quote: | Glenn
"Herb Martin" wrote:
"grmickelson" <grmickelson@discussions.microsoft.com> wrote in message
news:730C22F1-CD88-49B7-A04C-541316D77E1E@microsoft.com...
I need some help in what and how to configure my DNS. I am running
Server
2003 SBS.
I current have DNS Configured.
Local name is SYSCONDC01.SYSCONRESOURCES.LOCAL ip 192.168.1.10
I am also trying to set up my Domain name to also work which is
SYSCONRESOURCES.COM. ip 68.147.209.152
Ok, since they are two different names you just make
two different zones if you want to hold them both on the
same DNS server machine(s).
I need help in setting up the forwarding settings as everything I do
does
not work and I cannot get to my machine from the internet. I would
like
to
use my machine as the DNS providor for my domain (I hope I got the
wording
correct) but I am lost.
That's close enough, but (trust me) you do NOT want
to try to provide your own PUBLIC DNS server to
support that public name (SysConResource.Com).
That is MUCH better left at your Registrar where they
have multiple servers, 24/7 staff, fault tolerant hardware
etc.
Also, in any case you want to MENTALLY distinguish
between providing resolution for your OWN resources
(like above) to others, and for helping your users resolve
ALL names, both public and private.
They are really two different jobs, but most people new
to DNS miss this distinction since it is common for the
same DNS server to (end up having to) do both.
For YOUR users do it this way:
Set the INTERNAL computers to use ONLY your
internal DNS server (in their NIC->IP properties)
This will ensure they can resolve all internal names
BUT it might give them trouble with External (Internet)
names unless you setup forwarding correctly.
Set the INTERNAL DNS server to forward to the ISP
DNS server that your machine WOULD have used
if it didn't have a DNS server (and probably receives
from the DHCP if you use dial, cable, or DSL.
Here's a likely TRAP IF your server is also your router
to the Internet (if it isn't you can still use the idea to find
the correct ISP DNS for forwarding):
If that machine is a router it likely receives it's DNS
setting for the external NIC from DHCP (i.e., from
the ISP) and even your DC/Server itself must be
set STRICTLY to use only internal (itself) DNS
servers. (Remember we are going to forward to
handle the outside names.)
So, on that external NIC, find the setting for DNS server,
and WRITE IT DOWN. Then remove it, by overtyping
the value with again it's OWN address.
Now, you wrote down that external ISP DNS address, right?
THAT address is what you put in for the forwarder.
I have had myt Nephew help (he works on a large
server setup) but he has not been able to get it to work as well.
All I am really looking for is the setting/entries I need .
Note: at the provider of the domain name we have setup the Name server
to
point to server.sysconresources.com
Doesn't the provider give you the option of leaving the
DNS with them and using a web form to handle EXTERNAL
DNS name resolution?
If they do, use it. Otherwise consider changing to GoDaddy
or another big provider with this service.
--
Herb Martin
Glenn
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in