Alternate DNS resolution exceptions

I'm not sure if DNS is the correct approach to resolve this issue, but here's the situation.

We have a couple of sites that use integrated authentication (sharepoint for example).  When a user attempts to access the site from a non domain computer they will receive the generic login popup window.  These users are typically wireless guests which are on a separate subnet.  I'd like to direct those users to a TMG / ADFS proxy page that utilizes FBA authentication.

All subnets use the same DNS servers and I do not want to add a new one.  Is there a way to make that subnet resolve to another address or somehow do a redirect in IIS?

All dns / DHCP servers are windows 2012

Any help would be appreciated.
Thanks
LVL 1
eastmsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gheistCommented:
You must define AD sites, then you can select sites to prefer one or other DC and one or other exchange.
Dan McFaddenSystems EngineerCommented:
Since these are non-domain devices, this is not a DNS or AD thing, its an IIS item.

You can use IIS URL Rewrite module to catch the guest subnet and then redirect them to the desired page.  Though, if your guest devices connect thru a subnet other than the subnet defined in the rule, this config breaks down.

After you install the IIS URL Rewrite module, you can place this section into your web.config:

<system.webServer>
        <rewrite>
            <rules>
                <rule name="Redirect IP Range - 192.168.148.0/24" stopProcessing="true">
                    <match url="<TheGenericLoginPageNameGoesHere>\.html" />
                    <conditions>
                        <add input="{REMOTE_ADDR}" pattern="192.168.148.*" />
                    </conditions>
                    <action type="Redirect" url="/<TheGuestLoginPage>.html" redirectType="Found" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>

Open in new window


Just modify the section so that "<TheGenericLoginPageNameGoesHere>" is the URL of the guest login page and then update the redirect URL "<TheGuestLoginPage>"  to the name of your desired web page for the guests.

You can view/modify the rule thru the IIS Manager as well, after dropping the above section into the web.config file in the root of your web application.

Dan

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
eastmsAuthor Commented:
Thanks Dan,

I think that will work for the sharepoint site but not for the ADFS proxy.  Maybe I can create an action to rewrite the url and make a new internal DNS record for the external interface of ADFS
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.