I have an idea for a cool script.

[DWHS.net]

So here is the idea:

Make a script that scans the apache error log daily for the error:

lame server resolving your-main-domain.com ect..

Then when t finds one it create a a dns zone file for that domain and a specified i.p..

Then it scp's the dns zone file to your dns servers /var/named/ directory?

What do you guys think?



Chaze

[DWHS.net]

Nobody agrees?

[gorilla]

greta idea

[kosmo]

greta idea

Wasn't she Greta Garbo?

[gorilla]

Wasn't she Greta Garbo?

You know your women , that was to be expected from a greek gigolo

[Spiral]

So here is the idea:

Make a script that scans the apache error log daily for the error:

lame server resolving your-main-domain.com ect..

Then when t finds one it create a a dns zone file for that domain and a specified i.p..

Then it scp's the dns zone file to your dns servers /var/named/ directory?

What do you guys think?



Chaze

Bad idea .... creating such a script would allow ANYONE to install new zone files
to your DNS server by simply updating their domains to use your DNS servers.

This would of course open up a potential pandora's box of security problems.

I do have a similiar script installed on my server as a cronjob but instead of
blindly creating DNS zones when it detects the error message, it just simply
sends me an email message to let me know there is a domain out there
configured for our network that is not setup in our DNS. That way, I can
review it and determine if it is a domain that should be legitimately added
to our DNS servers or not.

[sawbuck]

I do have a similiar script installed on my server as a cronjob

Any interest in sharing it?

[rpmws]

is there a way to do wildcards with bind? have bind point normally (non) resolving domains to a particular IP? a way to catch traffic you normally would not be able to.

[Specks]

I don't think you can create a complete wildcard zone for bind to shuck all non-resolvable domains to. I'll have to find my Bind book and see if such a domain is possible. I don't think so though.

[Spiral]

I don't think you can create a complete wildcard zone for bind to shuck all non-resolvable domains to. I'll have to find my Bind book and see if such a domain is possible. I don't think so though.

Actually you can but what would be the point?

[DWHS.net]

Actually you can but what would be the point?

I was thinking to capture canceled domains traffic and to have a page show that the account is no longer active.

Also to not have lame server resolving errors.

Not a big deal but when you have thousands of accounts the traffic can ad up and help promote your company while helping the surfer too.

[Ishware]

Isn't it the case that if a request comes in that doesn't match anything in httpd.conf, that apache shows the server-wide default page? (i.e. "There is no website configured at this address")...

Seems like you could customize that page with your desired info... *shrug*

My apologies if this wouldn't apply to all cases. And sure, it'd only be html, but hey, it's a start.

[DWHS.net]

Isn't it the case that if a request comes in that doesn't match anything in httpd.conf, that apache shows the server-wide default page? (i.e. "There is no website configured at this address")...

Seems like you could customize that page with your desired info... *shrug*

My apologies if this wouldn't apply to all cases. And sure, it'd only be html, but hey, it's a start.

True but only if a dns zone exists for that domain name, this script would create the dns zone sending them to a i.p. or the default page.

If their is no dns zone then the connection goes to a page cannot be found error.