First of all, is there any best way to set DNS on our VPS? How to do that? I tried to follow the tutorial and even asked the VPS company to do it for me (two different company) but when they do that, I checked with DNSStuff.com, this is the result I get.
Error 1
ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
Error2
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
But my reseller account with another company show no such problem. At first I thought my first VPS company didn't know what they do, but it could not be that both company didn't know what they are doing when setting up the DNS of my VPS right?
So, there must be something that I need to say to them, so the lame nameserver error will disappear.
The messages in my logs indicate that my DNS server is configured incorrectly.
lame server resolving 'pobrdesign.com' (in 'pobrdesign.com'?): 209.40.198.107#53 lame server resolving 'pobrdesign.com' (in 'pobrdesign.com'?): 209.40.197.108#53
Here is a complete log from restarting named:
Code: shutting down stopping command channel on 127.0.0.1#953 no longer listening on 127.0.0.1#53 no longer listening on 209.40.198.107#53 no longer listening on 209.40.197.108#53 exiting zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42 zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700 zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42 zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN/localhost_resolver: loaded serial 1997022700 zone localdomain/IN/localhost_resolver: loaded serial 42 zone localhost/IN/localhost_resolver: loaded serial 42 zone pobrdesign.com/IN/external: loaded serial 2007081405 zone pobrdesign.com/IN/external: sending notifies (serial 2007081405) client 209.40.198.107#45926: view localhost_resolver: received notify for zone 'pobrdesign.com': not authoritative running
I configured my server through WHM initially. Here is my named.conf
Code: 1 include "/etc/rndc.key"; 2 3 controls { 4 inet 127.0.0.1 allow { localhost; } keys { "rndckey"; }; 5 }; 6 7 8 options 9 { 10 /* make named use port 53 for the source of all queries, to allow 11 * firewalls to block all ports except 53: 12 */ 13 query-source port 53; 14 15 // Put files that named is allowed to write in the data/ directory: 16 directory "/var/named"; // the default 17 dump-file "data/cache_dump.db"; 18 statistics-file "data/named_stats.txt"; 19 memstatistics-file "data/named_mem_stats.txt"; 20 }; 21 22 logging 23 { 24 /* If you want to enable debugging, eg. using the 'rndc trace' command, 25 * named will try to write the 'named.run' file in the $directory (/var/named). 26 * By default, SELinux policy does not allow named to modify the /var/named directory, 27 * so put the default debug log file in data/ : 28 */ 29 channel default_debug { 30 file "data/named.run"; 31 severity dynamic; 32 }; 33 }; 34 35 36 // All BIND 9 zones are in a "view", which allow different zones to be served 37 // to different types of client addresses, and for options to be set for groups 38 // of zones. 39 // 40 // By default, if named.conf contains no "view" clauses, all zones are in the 41 // "default" view, which matches all clients. 42 // 43 // If named.conf contains any "view" clause, then all zones MUST be in a view; 44 // so it is recommended to start off using views to avoid having to restructure 45 // your configuration files in the future. 46 47 view "localhost_resolver" 48 { 49 /* This view sets up named to be a localhost resolver ( caching only nameserver ). 50 * If all you want is a caching-only nameserver, then you need only define this view: 51 */ 52 match-clients { localhost; }; 53 match-destinations { localhost; }; 54 recursion yes; 55 56 zone "." IN { 57 type hint; 58 file "/var/named/named.ca"; 59 }; 60 61 /* these are zones that contain definitions for all the localhost 62 * names and addresses, as recommended in RFC1912 - these names should 63 * ONLY be served to localhost clients: 64 */ 65 include "/var/named/named.rfc1912.zones"; 66 }; 67 68 view "internal" 69 { 70 /* This view will contain zones you want to serve only to "internal" clients 71 that connect via your directly attached LAN interfaces - "localnets" . 72 */ 73 match-clients { localnets; }; 74 match-destinations { localnets; }; 75 recursion yes; 76 77 zone "." IN { 78 type hint; 79 file "/var/named/named.ca"; 80 }; 81 82 // include "/var/named/named.rfc1912.zones"; 83 // you should not serve your rfc1912 names to non-localhost clients. 84 85 // These are your "authoritative" internal zones, and would probably 86 // also be included in the "localhost_resolver" view above : 87 }; 88 89 view "external" 90 { 91 /* This view will contain zones you want to serve only to "external" clients 92 * that have addresses that are not on your directly attached LAN interface subnets: 93 */ 94 match-clients { !localnets; !localhost; }; 95 match-destinations { !localnets; !localhost; }; 96 97 recursion no; 98 // you'd probably want to deny recursion to external clients, so you don't 99 // end up providing free DNS service to all takers 100 101 // all views must contain the root hints zone: 102 zone "." IN { 103 type hint; 104 file "/var/named/named.ca"; 105 }; 106 107 // These are your "authoritative" external zones, and would probably 108 // contain entries for just your web and mail servers: 109 110 // BEGIN external zone entries 111 112 zone "pobrdesign.com" { 113 type master; 114 file "/var/named/pobrdesign.com.db"; 115 }; 116 }; Here is my /var/named/pobrdesign.com.db file:
Code: ; cPanel 11.6.0-BETA_15058 ; Zone file for pobrdesign.com $TTL 7200 @ 86400 IN SOA server.pobrdesign.com. support.pobrdesign.com. ( 2007081405 ; serial, todays date+todays 86400 ; refresh, seconds 7200 ; retry, seconds 3600000 ; expire, seconds 86400 ) ; minimum, seconds
pobrdesign.com. 86400 IN NS server.pobrdesign.com. pobrdesign.com. 86400 IN NS server2.pobrdesign.com.
pobrdesign.com. IN A 209.40.198.107
localhost.pobrdesign.com. IN A 127.0.0.1
mail IN CNAME pobrdesign.com. www IN CNAME pobrdesign.com. ftp IN A 209.40.198.107 pobrdesign.com. IN MX 1 ASPMX.L.GOOGLE.COM. pobrdesign.com. IN MX 10 ASPMX5.GOOGLEMAIL.COM. pobrdesign.com. IN MX 5 ALT1.ASPMX.L.GOOGLE.COM. pobrdesign.com. IN MX 6 ALT2.ASPMX.L.GOOGLE.COM. pobrdesign.com. IN MX 11 ASPMX4.GOOGLEMAIL.COM. pobrdesign.com. IN MX 12 ASPMX3.GOOGLEMAIL.COM. pobrdesign.com. IN MX 13 ASPMX2.GOOGLEMAIL.COM. server 14400 IN A 209.40.197.108 server2 14400 IN A 209.40.198.107
glaring issue that is keeping my DNS from working.
I have two servers in one of my datacenters that are giving off lame name servers. I have tried everything I could think of, as well as everything I could find online to fix these issues. Can anyone point me in a direction?
i got too many logs on Lame-server resolving i my log.
every second about 10-20.
Jul 23 11:31:33 ns1 named[15967]: lame server resolving '92-49-205-1.dynamic.peoplenet.ua.mydnsdomain.net' (in 'mydnsdomain.net'?): my.ip.add.ress#53 Jul 23 11:31:33 ns1 named[15967]: lame server resolving 'www.mydomain.com.mydnsdomain.net' (in 'mydnsdomain.net'?): my.ip.add.ress#53
so i turned of the logging and start search the web on possible reasons. However the only once i found where mostly "in case of the domain is not hosted on the server". But in my case the domains in questions are on my server and show in the log as lame server resolv.
They say it has to do with server is not authoritive for that domain.
So how i am gonna fix this?
With digs, and nslookups, i got not errors at all.
But if i try to change a DNS i got a message back from a provider saying that the domains is broken.
I just changed the server, and I can't make the new to work.
The server is CentOS 5 with WHM/cPanel.
The problem seems to be something with DNS / Nameservers - because the server doesn't resolve the domains.
Here is /etc/hosts:
Code: # Do not remove the following line, or various programs # that require network functionality will fail. 85.17.174.68 sv1.byteserv.net sv1 127.0.0.1 localhost Here is /etc/named.conf:
Code: include "/etc/rndc.key"; controls { inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; }; }; acl "trusted" { 127.0.0.1; 85.17.174.68; 85.17.174.70; }; options { query-source port 53; version "Top Secret"; dump-file "data/cache_dump.db"; statistics-file "data/named_stats.txt"; memstatistics-file "data/named_mem_stats.txt"; allow-recursion { trusted; }; allow-notify { trusted; }; allow-transfer { trusted; }; }; logging { channel default_debug { file "data/named.run"; severity dynamic; }; }; view "localhost_resolver" { match-clients { localhost; }; match-destinations { localhost; }; recursion yes; zone "." IN { type hint; file "/var/named/named.ca"; }; include "/var/named/named.rfc1912.zones"; }; view "internal" { match-clients { localnets; }; match-destinations { localnets; }; recursion yes; zone "." IN { type hint; file "/var/named/named.ca"; }; }; view "external" { match-clients { !localnets; !localhost; }; match-destinations { !localnets; !localhost; }; recursion no; zone "." IN { type hint; file "/var/named/named.ca"; }; zone "sv1.byteserv.net" { type master; file "/var/named/sv1.byteserv.net.db"; }; zone "byteserv.net" { type master; file "/var/named/byteserv.net.db"; }; zone "bujorel.es" { type master; file "/var/named/bujorel.es.db"; }; zone "directesa.com" { type master; file "/var/named/directesa.com.db"; }; zone "directoriospro.com" { type master; file "/var/named/directoriospro.com.db"; }; zone "gabiemi.com" { type master; file "/var/named/gabiemi.com.db"; }; zone "logisticexpress.es" { type master; file "/var/named/logisticexpress.es.db"; }; zone "windowsue.com" { type master; file "/var/named/windowsue.com.db"; }; }; The domain is www.byteserv.net Here is an report: [url]
And here it says I don't have an "A record for sv.byteserv.net" - but from cPanel I added the A record - or it should be added. [url]
1) I use DNSMadeEasy for a couple of my important domains so I can utilize their failover service.
2) I use my own nameservers for everyone else.
At my register (GoDaddy) I've added host entries to my domain (let's call it host.com) for ALL of my nameservers: DNSMadeEasy and mine. For example here are my host entries:
At the register I've then configured host.com to use the first five nameservers for itself, the DNSMadeEasy nameservers.
For less critical sites that I host I simply point them to ns1.host.com and ns2.host.com, my nameservers.
Now, here's the twist. If I use dig to look up www.host.com I get:
[root@lax1 ~]# dig +trace www.host.com
; <<>> DiG 9.3.3rc2 <<>> +trace www.host.com ;; global options: printcmd . 220048 IN NS D.ROOT-SERVERS.NET. ........................................... . 220048 IN NS K.ROOT-SERVERS.NET. ;; Received 228 bytes from 66.63.160.2#53(66.63.160.2) in 1 ms
net. 172800 IN NS J.GTLD-SERVERS.net. ........................................... net. 172800 IN NS G.GTLD-SERVERS.net. ;; Received 497 bytes from 128.8.10.90#53(D.ROOT-SERVERS.NET) in 74 ms
host.com. 172800 IN NS nsdme0.host.com. host.com. 172800 IN NS nsdme1.host.com. host.com. 172800 IN NS nsdme2.host.com. host.com. 172800 IN NS nsdme3.host.com. host.com. 172800 IN NS nsdme4.host.com. ;; Received 225 bytes from 192.48.79.30#53(J.GTLD-SERVERS.net) in 125 ms
www.host.com. 1800 IN CNAME host.com. host.com. 75 IN A 60.55.55.55 host.com. 86400 IN NS nsdme2.host.com. host.com. 86400 IN NS nsdme1.host.com. host.com. 86400 IN NS nsdme5.host.com. host.com. 86400 IN NS nsdme0.host.com. host.com. 86400 IN NS nsdme4.host.com. host.com. 86400 IN NS nsdme3.host.com. ;; Received 276 bytes from 123.123.123.123#53(nsdme0.host.com) in 68 ms BUT, if I lookup the nameserver (ns1.host.com) I get:
Code: [root@lax1 ~]# dig +trace ns1.host.com
; <<>> DiG 9.3.3rc2 <<>> +trace ns1.host.com ;; global options: printcmd . 218964 IN NS M.ROOT-SERVERS.NET. ........................................... . 218964 IN NS K.ROOT-SERVERS.NET. ;; Received 228 bytes from 66.63.160.2#53(66.63.160.2) in 1 ms
net. 172800 IN NS H.GTLD-SERVERS.net. ........................................... net. 172800 IN NS G.GTLD-SERVERS.net. ;; Received 497 bytes from 202.12.27.33#53(M.ROOT-SERVERS.NET) in 115 ms
ns1.host.com. 172800 IN A 60.55.55.55 host.com. 172800 IN NS nsdme0.host.com. host.com. 172800 IN NS nsdme1.host.com. host.com. 172800 IN NS nsdme2.host.com. host.com. 172800 IN NS nsdme3.host.com. host.com. 172800 IN NS nsdme4.host.com. ;; Received 241 bytes from 192.54.112.30#53(H.GTLD-SERVERS.net) in 151 ms
What I've realized is that the actual IP addresses for nameserver host entries come from a higher level server than my own, in this case H.GTLD-SERVERS.net. I guess this makes sense but I just hadn't realized it before. It looks like I don't even need to have record entries in my DNS records for the host nameservers.
Now for the question. Can I:
1) Remove my custom host nameserver entries from my register.
2) Add entries in my DNSMadeEasy records to specify the location of ns1.host.com and ns2.host.com.
3) Use the failover provided by DNSMadeEasy to also fail-over my DNS entries for my nameservers?
I know this would require one more hop if it works but it would allow me to provide failover ability to fifty domains without having to purchase the extra domains at DNSMadeEasy.
I see some errors about lame servers in messages log,and i noticed that look like adress of isp surfer domain beacuse i noticed domain of my isp listed also as lame name server.Here is example:
Nov 24 03:46:55 available9 named[7562]: lame server resolving '247.100.51.72.in-addr.arpa' (in '100.51.72.in-addr.arpa'?): 205.214.192.202#53 Nov 24 03:46:55 available9 named[7562]: lame server resolving '247.100.51.72.in-addr.arpa' (in '100.51.72.in-addr.arpa'?): 205.214.192.201#53 Nov 24 03:46:56 available9 named[7562]: lame server resolving '247.100.51.72.in-addr.arpa' (in '100.51.72.in-addr.arpa'?): 205.214.192.202#53 Nov 24 03:46:56 available9 named[7562]: lame server resolving '247.100.51.72.in-addr.arpa' (in '100.51.72.in-addr.arpa'?): 205.214.192.201#53 Nov 24 07:19:51 available9 named[7562]: FORMERR resolving 'ducksimilar.com/NS/IN': 203.93.208.87#53 Nov 24 07:19:51 available9 named[7562]: FORMERR resolving 'ducksimilar.com/NS/IN': 91.208.228.150#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host1.experienceexcept.com/AAAA/IN': 203.93.208.87#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host2.experienceexcept.com/AAAA/IN': 203.93.208.87#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host1.experienceexcept.com/AAAA/IN': 91.208.228.150#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host2.experienceexcept.com/AAAA/IN': 91.208.228.150#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host1.experienceexcept.com/AAAA/IN': 203.93.208.87#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host2.experienceexcept.com/AAAA/IN': 203.93.208.87#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host1.experienceexcept.com/AAAA/IN': 91.208.228.150#53 Nov 24 07:19:52 available9 named[7562]: FORMERR resolving 'host2.experienceexcept.com/AAAA/IN': 91.208.228.150#53
I have a domain hosted at godaddy.com and I decided to go with VPS hosting elsewhere. I have changed the nameservers to [url]and [url]at godaddy. I set up the reseller account in WHM but the nameservers point to something other than [url]I am trying to change them to the correct nameservers by using the "Nameserver IP Assigment" tool but it is taking literally forever. Is this normal?
Should I have to wait until it assigns an IP address to use the correct nameserver?
For some reason in WHM (root) (Fresh install) I'm trying to add a name server into ":2086/scripts2/listassignednsips" area and it just loads.... Never errors or anything just loads and loads for 30 minutes and never adds it. I have already add the IP's to the server. (6 IP's)
Have you come across this problem where you change the NameServer IP in '/etc/nameserverips' but the change does not reflect , instead it reverts to the old IP?
Doing the following fixed the issue for me.
Disable whois lookups for the nameserver ip manager via in WHM>Tweak Settings
and this domain mydomain.com is hosted from a nameserver called ns1.mydomain.com and ns2.mydomain.com
will this mean that:
the person who own mydomain.com owned his/her own webhost server?
and is that what is being called dedicated server? where I already did some research that would mean the whole server is owned by the 1 person/domain only?
I have been asking question to myself quite sometime now.. and hoping that this forum could help me in understanding this matter.
I just took out a VPS hosting plan with Hostican, but I'm a bit confused about whether I followed their instructions properly... please be patient
Their instructions said this:
Quote:
Please note that on our network a VPS is like your own private space on the network to work from. This is why we provide your account with two dedicated IP addresses that you will need to use to register your name servers with. Please view the below name servers and IP addresses that you should use to register them.
Now all my domains are registered with 1&1, who don't provide an option for creating private nameservers in their control panel. So, I created two subdomains (ns1 and ns2.mydomain.com) and then created A records for ns1 and ns2, pointing to the IPs supplied by Hostican. Then I changed the nameserver for my domains to ns1 and ns2.mydomain.com
After a couple of days, this seems to have worked - domains point to new VPS webspace and emails working. I'm worried whether I did this properly though, or whether I'm going to get problems in future with reverse dns and stuff?
My dating site sends an email notification to the user when they receive a message on the site. Many of the notify emails arent going to their destination.
In exim, I keep seeing this message:
failed for 550-unrouteable
mail domain "ns1.mydomain.com" 550 Sender verify failed
And this is when I added a new domain in Cpanel. Using nameservers with the following IPs: 66.21.113.11,66.21.114.11 Bind reconfiguring on serverprovider using rndc Created DNS entry for mydomain.com
I just got a VPS, (unmanaged...eh), and I seem to be having a problem with nameservers.
The current IP for the VPS is: [url]
Its set as the shared IP in WHM, so everything is pointing to that. I asked my host if the nameservers ns1.thehobbylounge.com and ns2.thehobbylounge.com should work (that is the domain for the account I am running under WHM/cPanel), and I was told that this was correct.
However my registrar gives me a validation error when I put in those nameservers for my domain.
I tried to follow these steps: [url]
But they seem to be already done...I think thats if your server isn't setup at all.
can't seem to figure out how the whole nameserver/DNS thing works.
My VPS is registered under a domain, say mydomain.com. So my nameservers on the VPS are registered under ns1.mydomain.com and ns2.mydomain.com, both assigned to the two IP addresses for my VPS.
The problem is, I'm trying to figure out how to get mydomain.com to actually point to my VPS from my registrar. If I type in ns1.mydomain.com and ns2.mydomain.com, it's just pointing to itself so it doesn't work.
I went throught WHM and I need to assign IP address to this Nameserver on the new server, and what will happen if I assign this IP address to the same Nameserver as in old server?
In this case,
1) Should I change the name of Nameserver to something else, such as following?
2) Or should I use IP address instead of using this English name? 3) Or should I wait until all the files are uploaded and assign this IP address to this Nameserver on the new box? I wonder what will happen if I do this, because there would be 2 different IP address to the same Nameserver in this earth!
CentOS with DirectAdmin (thanks to WHT for recommending this).
My problem is, I cant seem to "make" a nameserver and get it to work?
I have attached some .jpg. screenprints which I hope will help resolve my problem.
I hope you will look at the pictures and tell me what I am doing wrong.
I have followed the guide in DirectAdmin forum for creating a nameserver, but I still got problem. (I have not been able to post in there forum, cause I have not gotten a activate mail yet, so while I wait for that, I hope you will help me.)
I have waited a couple of days for the dns nameserver to update, but it is still not working.
I was with VPS Host A. When I wanted to have my domain name on the VPS from Host A, I simply entered the primary & secondary nameserver names at my registrars site and it was done.
Host A's service was poor, so I've started with VPS Host B. they created nameserver names for me at Host B's DNS for my VPS.
When I went to my Registrars site to entered these nameserver names, I was instructed to create an A record and a subdomain for each nameserver name.
I don't understand why it was simple with the first set of nameserver settings but not the 2nd ones.
The domain name for my first vps is different than my second vps.
The nameserver names from Host A didn't include the doamin name, for example Host A's were ns1.computer.com and ns2.computer.com and the nameserver names from Host B were ns1.mydomain.com and ns2.mydomain.com.
Could it be that it wasn't easy the second time because the nameserver names included my domain name?
check that my nameserver settings are correct for the following (some registrars do not allow me to change the DNS on some domains as it reports an error):
