Topic: DNS not resolving some addresses [Now Working - nothing changed]

[girkers]

My server is in Server only mode and is my DNS server for my local network. I was having some trouble recently access some websites so I thought I would check out what was going on. What is happening is that my SME server is not able to resolve certain addresses. To confirm this, I have tried the following commands:

• dig
• host
• dnsqr
• nslookup

and on all occassions I would receive the error message "connection timed out; no servers could be reached"

In my research I found this command:

Code: [Select]

env DNSCACHEIP=8.8.8.8 dnsqr a [fqdn]Now when I run this command I get this result ([fqdn] and [ipaddress] proper terms just replaced for privacy:

Code: [Select]

1 [fqd]n:
51 bytes, 1+1+0+0 records, response, noerror
query: 1 [fqdn]
answer: [fqdn] 83 A [ipaddress]
Can anyone help me "resolve"  my problem with DNS queries not working properly. I currently don't have anything in the Corporate DNS settings as per the usual spec.

Thanks

Girkers

Addendum:

Just found another post that reported similar problems and my problem is not a disk space issue, but here is the results of the requests asked in the other post:

Code: [Select]

[root@caine ~]# df -h -T
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/main-root
              ext3    913G  497G  370G  58% /
/dev/md1      ext3     99M   38M   57M  41% /boot
none         tmpfs    2.0G     0  2.0G   0% /dev/shm
[root@caine ~]# db configuration show dnscache.forwarder
dnscache.forwarder=service
    status=enabled
[root@caine ~]# db configuration show dnscache
dnscache=service
    TCPPort=53
    UDPPort=53
    access=private
    status=enabled


[CharlieBrady]

As a member of the Docs team, you should be well aware of this directive:

   Don't report problems here - Please report bugs and potential bugs in the bug tracker

Note that if you want someone to help you with this, you will need to identify the fqdn which is not resolving for you.

Your subject is misleading also - you describe problems with resolving a DNS name, but I see no evidence that queries are not being forwarded, only that replies are reported as not being received.

[girkers]

My status of Doc Team - I don't know how I got that status, it just appeared one day, don't be fooled 

Log as bug - I felt that this was one of those grey area as before posting I did a very thorough search and found that there were a couple of bugs filed that had related to this problem and they all had been return NOTABUG, thus the reason for posting it here.

not using the fqdn - I didn't really think it was relevant to know the FQDN as that is not really pertinant to the problem itself

Subject misleading - I have corrected this as you are correct.

On a side note I have just done a dig on the address on my Server and it is now resolving fine, nothing had changed, except time has past. Oh well.

[cactus]

My status of Doc Team - I don't know how I got that status, it just appeared one day, don't be fooled 

No, it does not just appear, it appears after your application for access to the wiki (docteam) has been granted.

Log as bug - I felt that this was one of those grey area as before posting I did a very thorough search and found that there were a couple of bugs filed that had related to this problem and they all had been return NOTABUG, thus the reason for posting it here.

This discussion has been raised over and over again. It is not what you feel, in fact it is quite simple: out of the ordinary, unexplainable behavior, for core functionality, especially when it starts without a intervention, should be reported to the bug tracker.

[girkers]

No, it does not just appear, it appears after your application for access to the wiki (docteam) has been granted.

I don't remember signing those papers, but it has been a long, long, long time since I have been active so I could have agreed to it.

This discussion has been raised over and over again. It is not what you feel, in fact it is quite simple: out of the ordinary, unexplainable behavior, for core functionality, especially when it starts without a intervention, should be reported to the bug tracker.

Thanks for the clarification.