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 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
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 am having some wacky stuff going on with my server. I run a Godaddy v-ded and according to them, the server is fine.
What i'm experiencing is, some of my domains are not resolving, some are. For the ones that are working that run via a database, every few hours, I need to restart mysql(or the server) to get them running again.
Linux OS: Kernel Version - 2.6.9-023stab044.4-smp Hardware Information - 3ghz xeon, 512mb, 20gig hd Software Version - fedora 7 Control Panel - WHM 11.11.0 cPanel 11.16.0-R18546
Since my local ISP hasn't updated yet, I'm still seeing the sites on the old server. I used a proxy (hidemyass.com) which seems to update all the time, and it said that it couldn't connect to the website (I usually use it to test a site's functionality before I can connect to the site)
What can I do to test where it's going wrong? The domains have been pointed at ns1.theplanet.com and ns2.theplanet.com already, and theplanet has created those nameserver entries for us already. I just don't want the domains to start resolving, only to find that something is broken....
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.
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 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]
We have a full rack of servers at an XO datacenter. Most of these servers consistently need to go out to the internet to retrieve various URLs. Essentially, the servers are spidering, like Google does.
Lately we have noticed that the DNS servers that XO provided, which are in the /etc/resolv.conf files for each server, have been randomly failing.
Is there any reason that I can't set the servers to go to the root and use that for DNS? I need to bypass the XO DNS servers some how.
One of the options that I am considering is setting up a dedicated server that can provide recursive DNS to my other servers and have that server ask the root DNS system for records when it is not in the cache.
The other option that I am considering is finding a company that I can buy the ability to do recursive dns on. The onyl one that I have found so far is DynDNS though, and I have been looking for about two hours.
[url]
If anyone can make any suggestions to how I can get around the XO issue I am having or provide suggestions to a provider of recursive DNS servers (not managed, unless recursive comes with it),
my DNS stop resolving, once a day i need to restart the service in cpanel/whm , what can be done to prevent that ?
its a fresh vps only cpanel is there and 2 domains with no pages just a simple under costruction index page . in CSF i have a Your Score: 106/112 in security , it firewalled and hardened
right now is using 299 of ram out of 512 burstable to 768
i have a weird problem with dns bind. i just setup a zone file and it seems [url]works but [url]doesnt work. i have also created a cname for www but still not working.
here is my zone file
$ttl 38400 domain.com. IN SOA ns1.domain.com. webmaster.domain.com. ( 1211542287 10800 3600 604800 38400 ) domain.com. IN A 67.223.229.117 ns1.domain.com. IN A 67.223.229.117 ns2.domain.com. IN A 66.249.8.117 domain.com. IN NS ns1.domain.com. domain.com. IN NS ns2.domain.com. www IN CNAME domain.com. ftp IN CNAME domain.com. mail IN MX 0 domain.com.
I have a local server named as 'EPBX' which monitors the working of the telephone system and makes their log entries. Recently its HDD partition got crashed due to which it was formatted and had re-installed Windows server 2003 after which I am facing some problems as given below:
- The IP address assigned to this server is 192.168.100.2. I am able to ping the IP but unable to take the console of the software from some other local PC.
- Also when I try to trace the IP using the tracert command first it resolves to the ISP's router and then to the server. But the router is not at all asigned a local IP. I have assigned a global IP to it. (Screen shot of the same has been attached)
- It would be very difficult for me to change the IP address
Just got set up with a new VPS and while looking to see if my IPs were blacklisted, I came across a RDNS warning. I've been on some form of shared hosting since I've been on the Internet, so much of the VPS stuff is new to me (though it is managed). Everything I've read says that RDNS is important for sending mail so the receiving end can verify where mail is coming from, but I thought I would ask here regarding my specific issue.
I've got four IPs on my account. The first ip, x.x.x.67, is the host IP(ie host.example.com). Most of my domains are using that IP at the moment since I just got set up, but I do have another domain on the last IP in my account, x.x.x.70. When I first did a RDNS check on my main IP I got a domain that I've never seen before, and all other IPs on my account don't resolve at all.
I sent a ticket off to the host, and they set the RDNS record correctly for the main IP on my account, but the other three still fail to resolve. When I asked the host about it in a ticket, the response that I got was
Quote:
Normally, we set RDNS for the main IP address to hostname of the server.
The RDNS for your server has been setup properly. Please get back to us if you need any further assistance.
So basically I'm clueless. Does it matter that the other three IPs I have available don't resolve at all? The domain on the x.x.x.70 IP, which doesn't resolve, is an e-commerce site that depends almost exclusively on e-mail for its business. Doesn't the lack of RDNS resolution mean that I'll be out of luck sending mail to AOL, Yahoo, Hotmail, etc etc on that account? Even though I don't have sites on the middle two IP addresses yet, I fully plan to put sites there within the next couple of months... could they have the same problem?
It's frustrating since I obviously have no control over RDNS records, and the host's staff is being a little obtuse about it.
We've just been told by our data centre that our server that we use to host our web design clients has been disconnected due to massive volumes of traffic from or to the server.
They said I will need to log into a KMV/IP in order to investigate.
I have no idea what I am doing and was wondering if there are any users out there that could give me some pointers in finding what is causing this DoS attack?
I'm hosting a few sites with LiquidWeb (freeteams.net and laxteams.net are the big ones), who's been a terrific host, but I occasionally have some issues trying to access my sites. It occurs only occasionally (maybe 10-20 people have let me know in the past year), but with users in different locations and on different ISPs. It seems to also only occur for a couple of hours.
When they try to type in a specific domain, it won't show up in their browser (browser-independent, I've tried it in Chrome, IE, and Firefox.) However, when they try the IP address directly, the site works. I have about 4 sites on one server, all with their own IP address, and the issue doesn't affect all the domains at the same time.
LiquidWeb says it's an ISP issue (they've checked all the settings on the server, and everything looks ok.) I tend to agree with them, because when I or my users switch from using their ISP's DNS server to OpenDNS' server, it works. However, it's happened at a number of different ISPs around the U.S., including universities, which makes me think there's something I can do to solve the problem. Also, I don't want users to have to change their computer settings.
Also, while I can't access the domain in the browser, I am able to ping the domain, and it will respond.
;; ANSWER SECTION: mp3-dash.com. 14400 IN A 89.46.102.100 mp3-dash.com. 14400 IN SOA ns1.mp3-dash.com.mp3-dash.com. admin@mp3-dash.com. 2009040602 86400 7200 3600000 86400 mp3-dash.com. 14400 IN MX 0 website.com. mp3-dash.com. 500 IN NS ns1.mp3-dash.com. mp3-dash.com. 500 IN NS ns2.mp3-dash.com.
;; AUTHORITY SECTION: mp3-dash.com. 500 IN NS ns2.mp3-dash.com. mp3-dash.com. 500 IN NS ns1.mp3-dash.com.
Searching for mp3-dash.com. A record at G.ROOT-SERVERS.NET. [192.112.36.4] ...took 30 ms Searching for mp3-dash.com. A record at F.GTLD-SERVERS.NET. [192.35.51.30] ...took 158 ms Searching for mp3-dash.com. A record at ns2.mp3-dash.com. [89.46.102.75] Query timed out (interrupted after 1,999 milliseconds) Retrying... Searching for mp3-dash.com. A record at ns1.mp3-dash.com. [89.46.102.74] Query timed out (interrupted after 2,000 milliseconds) Retrying... Searching for mp3-dash.com. A record at ns2.mp3-dash.com. [89.46.102.75] Query timed out (interrupted after 2,004 milliseconds) Retrying... Searching for mp3-dash.com. A record at ns1.mp3-dash.com. [89.46.102.74] Query timed out (interrupted after 2,000 milliseconds) None of the nameservers responded correctly.
I've got a VPS account & when I connect to sites on the VPS, more often than not the browser times out. I click again & the site comes through.
I use Firefox & have tried in other browsers with similar results.
The VPS has 384mb dedicated RAM, with 512mb burstable - not much I know but...
I was wondering about possible reasons - could it be simply not enough RAM, could it be a bottleneck with the hosting company, could it be a problem in the setting up of the nameservers? What would seem more likely?
It's a shame as the tech support have been superb but it's too risky to use for reselling.
Pinging perform.com.co [74.86.13.172] with 32 bytes of data:
Reply from 74.86.13.172: bytes=32 time=126ms TTL=49 Reply from 74.86.13.172: bytes=32 time=120ms TTL=49 Reply from 74.86.13.172: bytes=32 time=123ms TTL=49 Reply from 74.86.13.172: bytes=32 time=117ms TTL=49
Ping statistics for 74.86.13.172: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 117ms, Maximum = 126ms, Average = 121ms
Ocassionally some users have problems to connect the their websites, they can connect to the server via browser and can ping it and tracert the server IPs fine, they can also browse domains having a dedicated IP address. But they can't connect or ping their websites from their end, basically I think the domain name is not resolving.
From our end and the rest of users everything works fine.
Once I get a complain of this type I try whatever I can do
Check to see if their IP is not blacklisted Restart named service Restart apache service But most of the time this doesn't work at all.
Exactly as the problem comes it goes, nothing I did seems to have any effect on the solution. It goes and ocassionally reappears.
Would you suggest me what would I do to find where the problem is and try to solve it.
A client recently moved one of their domains to one&one (night mare I know) he then asked us to repoint the domain name to our servers using out name servers.
We have done this and it is not resolving to our server.
The problem is that the site is no longer showing and their emails are down.
I used a domain dossier and the DNS record looks like it should be changed but I'd like some confirmation on this.
I am having a problem with the installation of DomainKeys on my server.
I have a dedicated server from Hosting Matters and I have DomainKeys installed for another domain on the same server.
The problem that i'm running into is that I have a domain that is an addon account of another (basically hosted within a sub-directory of another account).
When I install DomainKeys via the cPanel I get no errors. It "appears" to work fine HOWEVER when I check the headers in Yahoo I get the following:
Authentication-Results: mta215.mail.re2.yahoo.com from=paperboyllc.com; domainkeys=permerror (no key) Received: from 63.247.138.128 (EHLO ws1.wpdnsgroup.com) (63.247.138.128) by mta215.mail.re2.yahoo.com with SMTP; Mon, 04 Aug 2008 21:27:03 -0700 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=paperboyllc.com; h=Received:To:Subject:Date:From:X-Mailer:MIME-Version:Content-Type:Message-Id:X ...
We are hosting a webservice application behind a Loadbalancer and the webservice is accessed via a ReverseProxy.However when we try to access the WSDL we see the endpoint loadbalancer IP coming in the response instead of the reverse proxy url.
