Topic: Contrib to fix DNS client names ("pc-00001" prob)

[rickjones]

I've built a contrib to overcome the local DNS client naming problem when SME is also the DHCP server. This is the one where the local machine names are hard-coded as "pc-00001" etc.

It's essentially a template fix to use DHCP lease information when building the DNS data file, and a service to watch when the leases change.

I'd like a few willing "guinea pigs" to try it out before I post it for all. It's not just that I want to be sure it works for other users, it's also the first serious RPM I've managed to build (I've been coding and scripting for more years than I like to think, just not got round to RPMs before!).

Drop me a mail if you're interested in giving it a try.

[mbachmann]

Fine, unfortunately this was the reason to decide not to use DHCP with, so i use static IP. Otherwise i would give it a try.

[Anonymous]

Drop me a mail if you're interested in giving it a try.

On it's way.

Birdey.

[rickjones]

After trial feedback (thanks all) and a few tweaks, this is now downloadable as an "RC" release.

http://contribs.activeservice.co.uk

A few other things there too that might be useful

[Reinhold]

Hi rick,

What does the "ident" reply look like after your dns fix?
(Note: I'd rather not see internal names handed to someone outside
and consider pc-00nn a security feature (however small))

Would you mind posting a:
sme-dhcp-dns-0.9-rc1.src.rpm

Thanks - keep up the good work

Reinhold

[rickjones]

What does the "ident" reply look like after your dns fix?
(Note: I'd rather not see internal names handed to someone outside
and consider pc-00nn a security feature (however small))

I don't know, to be honest! I'm not sure where ident gets its info from, but any ident from outside should only ever ID the SME box anyway. I'd suggest trying it on my server, but my ADSL link's gone pear-shaped today so there's not much chance of connecting

SRPM is available, there's a link at the bottom of my page "Browse source RPMs".

[Reinhold]

Hi Rick,

To further my cause...
As you can see below (excerpt from messages log) the original SME masquerades quite nicely even to the outside.
Trillian and mIRC otoh seem to give internal IP and names...
 
Standard - SME reply MAIL etc.
Month 23 11:39:39 mySME oidentd[654]: Connection from mirrors.kernel.org (204.152.111.222):40716
Month 23 11:39:39 mySME oidentd[654]: [204.152.111.222] (Masqueraded) Successful lookup: 1613 , 21 : user67

Trillian
Month 1 12:27:27 mySME oidentd[8502]: Connection from mx3.evanzo-server.de (62.67.120.120):50601
Month 1 12:27:27 mySME oidentd[8502]: [192.168.0.65] Successful lookup (by forward): 2535 , 110 : trilluser

mIRC
Month 08:39:52 mySME oidentd[24840]: Connection from operation1.nacamar.net (195.185.120.120):37161
Month 22 08:39:52 mySME oidentd[24840]: [192.168.0.67] Successful lookup (by forward): 1040 , 6667 : myNick

-----
Found the source rpm - THANKS
(seems I always have trouble with "the fine print" )

Regards
Reinhold

[msoulier]

I've built a contrib to overcome the local DNS client naming problem when SME is also the DHCP server. This is the one where the local machine names are hard-coded as "pc-00001" etc.

This is fixed in the latest e-smith-tinydns, available in the devel directory of any e-smith mirror.

Cheers,
Mike

[rickjones]

Hi Reinhold

Hi Rick,

To further my cause...
As you can see below (excerpt from messages log) the original SME masquerades quite nicely even to the outside.
Trillian and mIRC otoh seem to give internal IP and names...
 

I can only assume here that an IRC ident is requested over the open IRC connection that mIRC has set up (I don't use IRC so I've never played with this). Hence the client actually resolves the ident, so returns its internal IP, and whatever that name resolves to on the inside. I can't see how you can have valid internal name resolution, but also mask this.

Maybe some IRC-heads would know... ?

Cheers

[rickjones]

This is fixed in the latest e-smith-tinydns, available in the devel directory of any e-smith mirror.

Dang - I could have saved the time! Those updates are somewhat obscure, I still had to hunt around on FTP to find them. I guess the "devel" directory implies they're regarded as provisional/beta ?

I'll have to download and check it out.

[Anonymous]

I've built a contrib to overcome the local DNS client naming problem when SME is also the DHCP server. This is the one where the local machine names are hard-coded as "pc-00001" etc.

This is fixed in the latest e-smith-tinydns, available in the devel directory of any e-smith mirror.

Cheers,
Mike

And could you say when we can download the new version of sme with this update ?

I have the same pb with the DHCP server what must I do ? (it's a prod server)
use the rpm ?
or update the DNS ?

Thx for response

[rickjones]

And could you say when we can download the new version of sme with this update ?

I have the same pb with the DHCP server what must I do ? (it's a prod server)
use the rpm ?
or update the DNS ?

Well I've given this DNS update a quick try, and maybe I'm missing something but it doesn't seem to do a complete job. I can't see that it's monitoring live DHCP leases for a start.

I suggest giving my contrib a try, for me it does a better job than the update.