Hopefully someone can help clarify this.
I have a domain ie example.com registered with Go Daddy. I host the website with TSOHost so in my domain configuration, I have set the following NS records.
Nameserver 1: ns1.tsohost.co.uk
Nameserver 2: ns2.tsohost.co.uk
I am now able to serve the website both www and non www from this hosting package. I simply have an A record for example.com and a CNAME for www.example.com to point to example.com (this is being configured in the cpanel Advanced DNS Zone Editor). So now we have the website showing as expected and required.
I would also like to setup a kind of DDNS service using a different server entirely, (this will hold DNS records that I will create on the fly using a Radius database).
So I want to use the subdomain ddns.example.com for this DDNS service, ie bob.ddns.example.com for Bob (so that when I ping bob.ddn.example.com, I can alter the IP to 8.8.8. say). In Cpanel I have an A record for ddns.example.com and an A record for *.ddns.example.com to point to my server that will manage this, for example 85.214.214.214.
I have installed Bind on the server (currently using a digital ocean server for this, to which I have added ddns.exmaple.com as an A record to the droplet and *.ddns.example.com also), I have created a zone for ddns.example.com, within this I have set the ns record as the digital ocean details.
I have then added the following to my file /var/named/ddns.example.com.hosts
$ttl 38400
ddns.example.com. IN SOA ns1.digitalocean.com. jon#example.com. (
1414575123
10800
3600
604800
38400 )
ddns.example.com. IN NS ns1.digitalocean.com.
bob.ddns.example.com. IN A 8.8.8.8
When I ping bob.ddns.example.com on the server with bind installed I get 8.8.8.8, but when pinging for anywhere else I get the bind server IP.
Can I ask if what I am doing is possible ie, going from godaddy to tso, to another server and if so what NS records should I specify for bind? or is there something in the named config I need to change, I have set the following options in named.conf in an attempt to solve this issue.
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
allow-query { any; };
recursion yes;
I am aware that recursion may leave me open to DOS attacks and I intend to turn this to no eventually, but for the moment during testing I have left this to yes.
Any help or information would be greatly appreciated, I have been trying different variations of zone files etc without success, I am really though unsure as to if I am going in the right direction.
Hopefully I have made sense, but any further info I can provide, please let me know.
My first question would be - Are you sure you've updated the Registrar with this server as the DNS nameserver for this domain?
Use nslookup to find out:
# nslookup
> set querytype=NS
> server 4.2.2.1 (a DNS server on the Internet)
> ddns.example.com. (a closing dot helps avoid lookups using preferred search domains.)
and confirm that the Internet knows who to communicate with, and that your NS host is authoritative for the domain.
Next would be - Do you have any other nameservers up to "answer" for that subdomain, causing other problems?
BTW - glad to hear you fixed this issue!
Related
In the last month, my site no longer works on my computer or any computer connected to the same network that I use at home and I have tried other internet networks and the site doesn't work too, but strangely it works in some other networks!
The error message in the browser is : ERR_NAME_RESOLUTION_FAILED
I did not know the problem but when I looked at the site intoDNS I found 3 problems :
WARNING: One or more of your nameservers did not return any of your NS records.
------
You should already know that your NS records at your nameservers are missing, so here it is again:
ns77.domaincontrol.com.
ns78.domaincontrol.com.
-------
ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
208.109.255.49 216.69.185.49
Also, two months ago I moved my domain from Godaddy to Namecheap.
Please can you help me?
The domain's name servers are pointed to the servers of Godaddy, but there is no DNS zone for the domain there. You need to check what are the name servers of Namecheap (or another DNS hosting service) and point the name servers of the domain to these servers. Also you will have to create a DNS zone for the domain at the new DNS host (Namecheap or other of your choice) and create DNS records pointed to your web host's IP address.
If you only have a web site and no other services, like mail server you can only create two A records, like this:
Type: A
Host: # (or empty, it means the same)
Target (or Value, or Points to): ip.of.web.site
Type: A
Host: www
Target: ip.of.web.site
Okay, I'm running Apache Server 2.4.20 on an Arch Linux operating system. I currently have it setup and working in such a manner that requests from any outside connection get forwarded through my public static ip to the local ip thats connected to the server. Aside from setting up the port forwarding on my router and setting the /etc/http/conf/httpd.conf to Listen 80 I have not had to configure anything else to get the server running. Hmm, seemed very simple.
Now I want to move on to the next step in the process and host a domain name that I have purchased through my Apache Server. Basically, as of now, when you connect to my server it just displays my public static IP in the address bar. I want to set it up in such a manner that the domain name is displayed in the address bar NOT the IP to my server.
As of now I've been trying for three days to find the proper way to do this, it seems there is literally not a single guide anywhere that explains this step by step. I'm about 40 hrs of research into this. The bits and pieces I've gathered are
Use virtual hosts in httpd.conf file
Change the nameserver to point your domain to your server
I've tried every possible combination of virtual host combinations and trying to configure my nameserver its just not working, and im wasting huge amounts of time. Can someone please write a short concise guide from start to finish on setting up a domain name on an Apache Server. I don't need particular in depth explanations of whats being done, I understand the processes individually I just don't understand the process of setting it up.
So, I would love it if someone could whip up a simple example that shows the process from start to finish, again explanations of what your're doing at each step should be kept to a minimum as anyone going through this should have done they're research at this point.
EXAMPLE:
What I Have now:
Apache Server IP: **234.34.23.2**
Someone types this in and they get served your index.html page and this IP shows in the address bar.
What I'm trying to get too:
Purchased Domain Name: www.example.com
Now when someone types this in the address bar they get served that same index.html page and this domain name remains in the address bar.
Note: I'm trying to do this for only a single domain, so I will not need an example that involves multiple virtual hosts.
Your research was/is accurate. All you have to do is exactly the following:
Use virtual hosts in httpd.conf file
Change the nameserver to point your domain to your server
DNS/NameServer configuration
In your DNS settings, set the A and AAAA (if you have IPV6 values) to point to your IP:
Host: #
Value: 234.34.23.2
TTL: 3600 (seconds)
Save the above and refresh your machine's DNS cache. Now, going to www.example.com should try to open 234.34.23.2. If it doesn't, you can set the CNAME value for www to be the same as your A value by:
Host: www
CNAME: #
TTL: 3600 (seconds)
Again, reload your DNS cache and try.
VitualHost
For setting up Apache so that it knows which files to server for the www.example.com domain, in your httpd.conf file, add the following section:
Listen 80
<VirtualHost *:80>
DocumentRoot "/www/example"
ServerName www.example.com
ServerAlias example.com
<Directory "/www/example">
AllowOverride All
Options All
Require all granted
# Any other directives
</Directory>
# Other directives here
</VirtualHost>
Reload the Apache server (or restart). That is it.
I have a VPS from myhosting.com with Plesk 11. I've set up dns in windows plenty of times but for the life of me I can't seem to get this working through Plesk. Here are my settings through Plesk and Godaddy... I asked myhosting about the setup and they said as far as they can see it seems correct but for the life of me the site will not resolve... Any help would be much appreciated!!
Plesk:
GoDaddy Host Names:
GoDaddy Nameserver Settings:
Enter your domain name here http://who.godaddy.com/ and in results:
Check "status" - should be ACTIVE
Check "Name Servers" it should be ns1.v...v.com, ns2.v...v.com
Check that ns1.v...v.com or ns2.v...v.com can be resolved by command:
nslookup ns1.v...v.com
I suppose that it will be NOT resolved because your NS servers are placed in zone which can be resolved yet.
The easiest way is to use some another DNS servers, maybe GoDaddy or some other DNS hoster.
Or you can make a trick:
change domain's DNS servers to GoDaddy DNS servers
In GoDaddy's domain management panel add in DNS zone records with: ns1.v...v.com, ns2.v...v.com
Wait until you can resolve ns1.v...v.com and ns2.v...v.com - it's about 24 hours.
Switch domain's DNS server back to ns1.v...v.com and ns2.v...v.com.
Wait until changes will be visible by other DNS servers like Google:
nslookup ns1.v...v.com 8.8.8.8
All should works now.
When troubleshooting DNS issues (specifically whether a domain is resolving), what is the proper way to check so that you get accurate results? DNS info is cached throughout the internet, and different machines (like local machine) or service (like pingdom) has different results.
How to check the DNS so that you know what you will get after it propagates?
Working with Heroku and CloudFlare.
In most common cases you can use tools such as: dig or host. Both tools are made for query name servers to retrieve info. You can also use a simple "ping something.domain.com" in order to see if IP has changed. But I suggest you to use different DNS's on the computer you're using to test. Actually Google DNS replicate so fast ( 8.8.8.8 ).
Not on purpose DNS poisoning: Keep in mind if you're pinging something that is recently configured/changed on your name server and still not propagated you'll "poison" the DNS's cache and this data is going to expire, but later...( Always depending on domain name TTL's of course ).
Using a new DNS wich never has known that domain you're sure the request is made for the first time and it's going to be made without asking any cache.
Example:
To get all the DNS servers for domain.com:
$ host -t ns domain.com
domain.com name server ns2.domain.com.
domain.com name server ns3.domain.com.
To ask a domain name for something.domain.com:
$ dig #nameserver something.domain.com
You can also ask for TXT, CNAME types and so on...
Examples:
AXFR retrieval test:
$ dig #domainname domain.com AXFR
Or get all Mail Exchange (MX) server for a domain:
$ host -t MX domain.com
domain.com mail is handled by 10 smtp.godo.com.
domain.com mail is handled by 20 smtp2.godo.com.
Hope it helps.
Cheers! :)
http://en.wikipedia.org/wiki/Nslookup
To get a "Non-authoritative" answer from your local name server that would be e.g.:
nslookup test.com
To check the name server where the domain is listed that would be e.g.:
nslookup test.com nameServerOfTest.com
I hope you'll forgive me for thinking that configuring a DNS server would be easy. It turns out it is quite hard... especially if you never did it before.
To recap a little, I previously asked if someone could recommend a personal DNS server for Windows XP for use in a development project.
My basic wish is to host a DNS server that represents the following lookup table:
Address | IP
------------------+--------------
*.devdomain1.dev | 192.168.10.2
*.devdomain2.dev | 192.168.10.2
Do you know how to setup this in BIND 9? Or maybe there is an easier solution that I've overlooked. I know I could add the individual subdomains in my HOSTS file but since we have a lot of subdomains which has to be maintained on several dev machines I would rather have a simple wildcard setup.
A zone file like this should suffice (on my system this would be in /etc/bind/zones/devdomain2.dev.hosts)
devdomain2.dev. IN SOA localhost. johannesh.devdomain2.dev. (
1102522753
10800
3600
604800
38400
)
devdomain2.dev. IN NS localhost.
*.devdomain2.dev. IN A 192.168.10.2
Then my /etc/bind/named.conf.local would reference this as follows
zone "devdomain2.dev" {
type master;
file "/etc/bind/zones/devdomain2.dev.hosts";
};
(Note you could adapt this just wildcard .dev domain entirely, or set up another zone for devdomain1)
How far have you got?
You could just create a zone for .dev and use a wildcard record