DNS Error 4004 and 4015

[dzbom]

Hi All

I got this issue currently, I have been searching for the solution, and reading a lot of Tags and Threads from this helpful forum as well. But I still can't find the solution for my particular case.

Here is our system

1X 2003 server AD integrated - Domain controller
1X SQL server - 2003 member serrver.

That is it.

When I looked at the DNS event with the filter, the error 4015 has started since the server was first built. And there were about 4 DNS ISP IP address in TCP/IP properties, I already took them off, so that there is only IP address which is pointing itself 192.168.0.1.
And it happens randomly anytime it likes, and it stops DNS server, only way to get DNS server back on line is 'RESTART" the server and that is a pain.

So is it because there is only one DC with DNS? please confim.
Any reply would be appreciated.

Cheers

[Meinolf Weber]

Hello dzbom,

Did you also checked this one:
http://help.lockergnome.com/windows2...ict455051.html

typo in the doc 4014 is 4015

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Hi All
>
> I got this issue currently, I have been searching for the solution,
> and reading a lot of Tags and Threads from this helpful forum as well.
> But I still can't find the solution for my particular case.
>
> Here is our system
>
> 1X 2003 server AD integrated - Domain controller
> 1X SQL server - 2003 member serrver.
> That is it.
>
> When I looked at the DNS event with the filter, the error 4015 has
> started since the server was first built. And there were about 4 DNS
> ISP IP address in TCP/IP properties, I already took them off, so that
> there is only IP address which is pointing itself 192.168.0.1.
> And it happens randomly anytime it likes, and it stops DNS server,
> only
> way to get DNS server back on line is 'RESTART" the server and that is
> a
> pain.
> So is it because there is only one DC with DNS? please confim. Any
> reply would be appreciated.
>
> Cheers
>
> http://forums.techarena.in
>

[dzbom]

Hi

Thanks for your reply. I did have a look this solution but we don't have "." root zone at the first place. So we can rule out this.

I am still seeking for the solution.

Cheers

[Meinolf Weber]

Hello dzbom,

More then one option is here:
http://www.eventid.net/display.asp?e...ce=DNS&phase=1

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Hi
>
> Thanks for your reply. I did have a look this solution but we don't
> have "." root zone at the first place. So we can rule out this.
>
> I am still seeking for the solution.
>
> Cheers
>
> http://forums.techarena.in
>

[Jorge Silva]

Hi
If this error is at system startup you can ignore it.
Or you can point that server to other available DNS and check if the error
still happens.
--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb665a73b8c9ce613a553196@msnews.microsoft.com...
> Hello dzbom,
>
> More then one option is here:
> http://www.eventid.net/display.asp?e...ce=DNS&phase=1
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
>
>> Hi
>>
>> Thanks for your reply. I did have a look this solution but we don't
>> have "." root zone at the first place. So we can rule out this.
>>
>> I am still seeking for the solution.
>>
>> Cheers
>>
>> http://forums.techarena.in
>>
>
>

[dzbom]

To Meinolf

Thanks for your link and reply. I have been there and tried all of them but no go.

To Jorge

Thanks for your suggestion, as I mentioned early, it happens randomly and I does not happen when start up and unfortunately I have only one DC with DNS :(.

Much appreciated your replies.

Please help. Thanks

[Jorge Silva]

run dcdiag and netdiag check for errors.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"dzbom" <dzbom.2xjgfe@DoNotSpam.com> wrote in message
news:dzbom.2xjgfe@DoNotSpam.com...
>
> To Meinolf
>
> Thanks for your link and reply. I have been there and tried all of them
> but no go.
>
> To Jorge
>
> Thanks for your suggestion, as I mentioned early, it happens randomly
> and I does not happen when start up and unfortunately I have only one
> DC with DNS :(.
>
> Much appreciated your replies.
>
> Please help. Thanks
>
>
> --
> dzbom
> ------------------------------------------------------------------------
> dzbom's Profile: http://forums.techarena.in/member.php?userid=31604
> View this thread: http://forums.techarena.in/showthread.php?t=824184
>
> http://forums.techarena.in
>

[dzbom]

Hi Jorge

I did that too that is how I found the problem with 4 ISP DNS IP address sitting in the TCP/IP properties, I already got rid of them from TCP/IP properties. However I am not expert on dcdiag and netdiag, perhaps I run them again and post here for experts to have a look. Thanks for that

Cheers

[dzbom]

Hi all

I read and read thru 2 dcdiag and netdiag logs I could not find any errors, howver I am hoping that I fixed this issue. What I did was that I rang the ISP to find out the DNS server IP for name resolution, they gave me 2 IPs (primary and second) and they are totally different from the ones in our DNS server and DHCP server, so I think because the DNS server could not resolve those wrong IP address ones in our system. it gave that error.
Let see how it goes this time. I will update so that it would be good for everyone.

Cheers

[Jorge Silva]

great.

--

I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

"dzbom" <dzbom.2xm03g@DoNotSpam.com> wrote in message
news:dzbom.2xm03g@DoNotSpam.com...
>
> Hi all
>
> I read and read thru 2 dcdiag and netdiag logs I could not find any
> errors, howver I am hoping that I fixed this issue. What I did was that
> I rang the ISP to find out the DNS server IP for name resolution, they
> gave me 2 IPs (primary and second) and they are totally different from
> the ones in our DNS server and DHCP server, so I think because the DNS
> server could not resolve those wrong IP address ones in our system. it
> gave that error.
> Let see how it goes this time. I will update so that it would be good
> for everyone.
>
> Cheers
>
>
> --
> dzbom
> ------------------------------------------------------------------------
> dzbom's Profile: http://forums.techarena.in/member.php?userid=31604
> View this thread: http://forums.techarena.in/showthread.php?t=824184
>
> http://forums.techarena.in
>

[dzbom]

Hi all

Update: It seems OK now (touch wood), now it only happens when restarting server, and as someone already said, that can be ignored.

Thanks all

Cheers